yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] arqileing:
Yes is the same. May be you have wrong drivers for Windows 8. Try a pc with windows 7.
[Miscellaneous Android Development] thetox2:
I have two PCs with Windows 8, and one with Kubuntu 14.04.

Can I try it on a VMWare virtual Machine with Windows 7?

Thanks in advance?
[Miscellaneous Android Development] arqileing:
Why not? You can try!
[Miscellaneous Android Development] thetox2:
I can't do it!!! :(

I downloaded the ROM from the link you gave me.

I installed my old Windows 7 on my VMWare virtual machine.

The phone gets recognized, but I get the following error while flashing (see the image link below):

Screenshot image

This post suggested using an older version of SP Flash Tool. I tried it, but it didn't work for me!

Can anyone help me?! :(

Please...

Thanks in advance.
[Miscellaneous Android Development] arqileing:
Try to selct "Da dl all wit check som with all check som and press firmware upgrade. But you will lost everything in internal memory.
[Miscellaneous Android Development] thetox2:
I flashed it with different rom. To be more precise, it is this ROM: http://www.needrom.com/download/cubot-one-turbo/

It seems that I have MT6589T version (turbo version) with original firmware version 0.8.

My bad... I shouldn't have been installing these ROMs, because the first post says: "Do not install Roms made by me on a Cubot One with original Rom Version 0.8 and up". And mine was 0.8.

Anyways, thanks for your help. And I'll try DA Dl option if this error shows up again (I don't care about the internal memory anyways... ;) ).
[Miscellaneous Android Development] arqileing:
If you can't flash miui than you can try https://cloud.mail.ru/public/ce4e5624516b/CUBOT ONE_D1_V0.8_20140124_MJK-1.rar . Is your original rom.

---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------

If you can't flash miui than you can try https://cloud.mail.ru/public/ce4e5624516b/CUBOT ONE_D1_V0.8_20140124_MJK-1.rar . Is your original rom.
[Miscellaneous Android Development] Mbariah:
Hi guys i need some help..am still trying to remove the 32fps limit on my friend's TS7 1.5Ghz...i found some info on a russian forum and despite google and bing translators, it doesn't make sense..so here it is..can anyone speaking russian help?...

Стоковая(заводская) прошивка под SP_Flash_ToolTronsmart TS7 8GB*версия*здесь, -*у меня эта прошивка не работает, ядро в ней с разблокированным FPS! Прошивка будет работать, если её установить следующим образом. Качаете эту прошивку, прошиваете, далее качаете прошивку TS7 4GB версии, и прошиваете из неё только BOOT и UBOOT. Всё прошивка Tronsmart TS7 8GB версии востановлена. Если не прошить дополнительно BOOT и UBOOT от 4GB версии, то не будет изображения.

P.S. i am not sure if its okay posting on xda in another language so here's my apology in advance to any rules broken..don't ban me[emoji16]

Sent from my Jiayu G4S octacore
[Miscellaneous Android Development] Maximus1a:
not all cubot one and devirates are able to display more than 32fps. you won´t realy benefit from unlocking fps limit. it only drains your battery and makes your digipenis in antutu etc. a little bit longer.
[Miscellaneous Android Development] Mbariah:
It's not really about benchmarks but just to get rid of the annoying lag that is there on every launcher,settings page and that's on every rom i've tried...and to make matters worse,even most apps and games are affected..flappy bird plays at what i think is 3-8fps...u can imagine Asphalt..i had an mtk6589 and it was miles ahead on performance..so i think its kernel issue considering it's an mtk6589T..

Sent from my Jiayu G4S octacore
[Miscellaneous Android Development] bigrammy:
Hi bro,

Do you have a backup of the stock boot.img and uboot.img a matching pair? :fingers-crossed:

If so reflash them with spflashtool, cwm or twrp recovery. :good:

You can then try flash my ROM which is over on needrom.com Cubot by bigrammy Here I have had very good reports from TS users. :)

Be sure to swap out (change) the boot.img contained within the zip file with your own STOCK boot.img before you flash it. :cyclops:

Be sure to do a full wipe data, cache, delvik cache. I also recommend a clean install so please do not restore data from another ROM. ;)

Be sure to change the default storage to Phone Storage or the Google apps will fail to update. (Settings/Device/Storage) :D

:cool:
[Miscellaneous Android Development] Mbariah:
Tried this but didnt work..still lagging..unless someone mods the kernwl i dont think the issue is going away

Thanks anyway...

Sent from my Jiayu G4S octacore
[Miscellaneous Android Development] thetox2:
Cubot One with firmware v0.8 and MT6589T 1.5GHz CPU

If you have Cubot One with firmware v0.8 and MT6589T 1.5GHz CPU (to be exact, my phone is: G800_CUBOT_D1_V0.8_20140124_MJK) and want to flash any custom ROM do this:

1) Flash your stock ROM for Cubot One G800_CUBOT_D1_V0.8_20140124_MJK

2) Root your phone (you can do so with Eroot)

3) Flash v0.8 recovery version using MobileUncle application, and then boot into recovery (power off your phone, then hold power button + volume up button until you get the recovery menu)

4) Make a full backup of your ROM (with your newly installed recovery from step 2) with MTK Droid Tools

5) Boot into recovery, wipe user data, wipe cache, wipe dalvik cache and flash your new ROM from .zip file (you can find custom/official ROMs here and here)

6) After flashing power off your phone and flash your Boot.img from backup you made in step 3 (When you make backup you get MT6589_Android_scatter_emmc.txt file and all .img files --> Open SPFlashTools, load scatter file from backup, untick EVERYTHING, tick only BOOTIMG, locate the Boot.img file from backup by double clicking on the name "BOOTIMG" text in SPFlashTool, and than click Download and connect your phone on USB while its powered off and wait for process to complete)

7) Boot your phone into recovery again, and wipe user data, wipe cache and wipe dalvik cache again

8) Reboot your phone

9) Give it at least 3-5 minutes for the new ROM to load when you boot it for the first time (do not play with your new ROM yet, just give it 5 minutes until it's loaded 100%)

10) Enjoy your new custom ROM :)

I do not guarantee that this will work for everybody, but it worked for me!

I successfully flashed this ROM using the steps described above.

If you do these steps you are doing them on your own risk - I am not responsible for any eventual damage on your phone.

Happy flashing!

Note: this is the source from where I got the idea to do these steps (READ COMMENTS from user Florin Ovidiu Matei and Lukáš Beran): http://www.youtube.com/watch?v=1Jjlc6cRSv0

I hope this will help somebody...

I won't be able to test any ROMs other than this ROM, because this phone is not mine and I need to give it back to my beautiful girlfriend. :)

Sorry I didn't get the chance to test this method a bit more. I hope this will be helpful to somebody and I hope that one using this method won't have any troubles/issues.

***UPDATE***

I tried another ROM and it is flashable with the above method. ;)

Cheers
[Miscellaneous Android Development] dave..:
Hello

I've made a thread for v1.3 Here !!

Would you be so kind to add it on top of your page. [MENTION=1124043]Maximus1a[/MENTION]

please also add these:

v1.5!

v0.8 turbo

(your thread)

cheers

dave
[Miscellaneous Android Development] juan186:
I can't calibrate my battery. I have tried the app battery calibration, from the CWM recovery, removing the file batterystats.bin

Any solution? Please, help me, I don't know how I solve my problem

I have the cubot one turbo with the new screen, and the firmware 1.3
[Miscellaneous Android Development] y2imm:
This has probably already been asked, but anyway...assuming one has the other mad skills required to build an Android ROM, is there currently a roadblock to doing so ie a lack of manufacturer support?...what stops a person with the requisite time, knowledge and skills from building an Android L ROM for this phone?...are we (owners) are in a position where we will most likely never see an upgrade past 4.X.?...
[Miscellaneous Android Development] Maximus1a:
if you can build your own kernel from scratch and have drivers for the used hardware you can build your own lollipop kernel.

MTK and Cubot won´t release any sources for the old 6589(T) phones to build custom Kernels.
[Miscellaneous Android Development] paragraf:
SD card swap

Hello Everyone!

I would like to swap my sd card with the phone storage. At least I think it would solve on of my problems. The phone currently forgets some settings after I reboot (like choosen input type ... I use swiftkey but after reboot only the android keyboard pops up, I have to enable again swiftkey keyboard and reset it to be used... and some other stuff have to be reconfigureg again after every reboot).

A found the zip which would contain the swap, but I don't know how to install it. With cwm it fails. So if someone was able to apply it, I would appreciate a short guide how could I do it too.

I use the 0.8 ROM currently.
[Miscellaneous Android Development] Maximus1a:
after a long time i decided to make a new rom.

all info can be found in Post 2.

have fun.
[Miscellaneous Android Development] paragraf:
Hello,

I havve tried to install your new MIUI on my Cubot One (originally v0.6, later installed v0.8) but I didn't boot up. Waited for almost half our to boot up, but only the CUBOT logo was there. Tried to restart it with battery take out and put it back. No change.

Do you have any idea what could be wrong ?

Thank you in advance
[Miscellaneous Android Development] Maximus1a:
did you wipe your phone before flashing?
[Miscellaneous Android Development] paragraf:
Yes, made a full wipe before the update and wiped the cashe and the dalvik after the update.

Is it posible the second wipe caused the problem ? I used this method with the Stock ROM install too, as one of my friend recomended it, and there was no problem with that at all.
[Miscellaneous Android Development] Maximus1a:
wiping after flashing is not needed.

the correct way to flash a rom is: full wipe + dalvik wipe -> flash zip -> reboot

wiping after flashing should not harm but is needles.

maybe you should logcat over adb your phone while booting.
[Miscellaneous Android Development] paragraf:
Can you please explain this part (short step by step): "maybe you should logcat over adb your phone while booting."

By the way, I'm using CWM which is compatible with the v0.8 ROM (the one in main thread causes IMEI lost ).
[Miscellaneous Android Development] Maximus1a:
please google for "logcat over adb"

btw. ..... you are running 0.8? did you ever tried successful 0.4? i think your phone is not compatible.
[Miscellaneous Android Development] paragraf:
As I remember originally it came with 0.6 ROM, it was one of the first Turbo version Cubot Ones in Dec 2013. I have sucessfully installed the "Original FW CUBOT ONE T Card Upgrade Package.zip" before on the #1 post.
[Miscellaneous Android Development] Maximus1a:
weird...

an old device prior 0.8 should have problems running 0.8 and up roms and vice versa.

does yor lights sometimes flash while your are in bootloop?
[Miscellaneous Android Development] paragraf:
I don't remember for such thing, but I'm installing right now the necessary softwares to be able to run logcat over adb. After next install I will look carefully for every event what is happening during the whole process.

I had such problem since I tried before install 0.8 the first time, that the phone after every boot forgets some setup (like it forgets I have installed Swiftkey and I alwas have to enable it again in the keyboard; also forgets every before added accounts which is not google acc... for example Viber, Facebook but as soon as I start the application the account appears again in the Accounts panel in the System Settings).
[Miscellaneous Android Development] vuralemre:
I think i installed wrong rom. Cubot one has a reverse touchmatic.

Hardware buttons dont work. I need a solution or nand flash backup..

Stock roms or custom roms dont solve. What can i do to fix that..??

Thak you..
[Miscellaneous Android Development] xektop:
Hello [MENTION=3924647]bigrammy[/MENTION],

I also have this problem. I have Cubot but I am not sure if it is T version. It is from the first ones with the old displays. for sure it is 1,5Ghz if it helps.

Again like him I had issues with GPS and what I did is replace the boot.img.

Everything is fine and fast, but I am not able to choose different languages inputs. I select them but when I go back and check them again they are unselected.

What I did as temporary solution is install swiftkey and disable Android Keyboard and AOSP Keyboard > restart the phone. Now there is only one choice and it is swiftkey and there I can change everything. and customize. So the workaround works fine for me, but just wanted to point out this is not a single user issue.

Maybe it has something to do with the changing of the boot.img but I am by no means even on noob level. I just flash and consume.

Thank you for your work and if you have suggestions please do tell :)
[Miscellaneous Android Development] xektop:
Hello guys,

after testing some roms I stumbled on this:

https://drive.google.com/file/d/0Bxs-ooUqJga-VUdBSWZDaHFMVFk/edit

LewaOS_5.1T+_14.03.21_port_Legiondark from the 4pda forum.

It is working great on my Cubot One with the old display.

I guess Bigrammys and Androidias Roms are not for my device: The camera is not focusing on both roms and with bigrammy I have several more issues.

The only problem I have is that SIM 2 cannot be changed to have 3g Services and works only in 2G.

I have read that there are patches for xperia: http://www.informationlord.com/dual-sim-3g-switch-xperia-c-phones/

obviously this patch did not work for the cubot.

Is there someone who can create such patch in order to enable SIM 2 for 3g Services?

Worst case scenario I order a mini Sim for SIM1 and change the sim cards places :)

btw. no apps could enable the 3g on sim 2 so it is kernel related issue.

Thank you in advance!
[Miscellaneous Android Development] bigrammy:
For my ROM do a full manual wipe system/data/cache/dalvik

Make sure you have a cwm/twrp backup of your stock boot.img.

Flash my rom zip

Then go restore and restore your Stock boot.img Only. ( I know boot.img's can become mixed up when flashing roms so be sure it's your own stock boot.img and not from a custom rom )

Reboot to system and wait do not touch anything until 2 mins after it boots up.

follow the setup and don't skip anything.

Go straight to settings/storage and set your default storage to let system decide.

Check all is working wifi etc then do a full reboot (Power off totally) not a quick reboot.

:fingers-crossed:

Update any apps one at a time manually it's an old rom and lots of apps will want updating all at the same time this can cause problems when you select update all (Batch install)

I don't own the phone anymore but I see the guy I sold it to and he says he's had zero/none issues
[Miscellaneous Android Development] FX_fighter:
Do you have news about the release? Waiting for it ;) Thanks!
[Miscellaneous Android Development] bigrammy:
It was released a long time ago here http://www.needrom.com/download/cubot_one_xperia-c/ ;)
[Miscellaneous Android Development] FX_fighter:
Wow, i didn't see it, Thank you very much! i've tried CUBOT ONE MIUI 4.08.29 but have some problems with installing gapps. At the moment trying the cubot one xperia c port.
[Miscellaneous Android Development] djekan:
Is dead this device, no more ROMs or Port"s?

Thank you
[Miscellaneous Android Development] bigrammy:
Certainly not dead as this is a great little phone :good:

It's a good candidate for for some dev work but most are probably busy with newer devices me included. :(

I will be revisiting this phone when less busy. :cool:
[Miscellaneous Android Development] djekan:
Hello,

I need some help, i´ve a problem on my cubot one 1.5 Turbo, after flash stock 0.8 firmaware all OK, but now, i want instal a MIUI rom, but...

ROOT - OK

Istall custom recovery -OK

Flash a MIUI ROM (or other´s) errors on recovery, can't mount /emmc

Any idea to fix it???

thank you!
[Miscellaneous Android Development] djekan:
Solved, flashed the stock v0.3 and all OK,

Enviado do meu Moto G 2014 através de Tapatalk
[Miscellaneous Android Development] gintama_me:
Hi.

why there is no any ROM with android 4.4 ?

There is Cyanogenmod with android 4.4

There is [ROM][UNOFFICIAL][WIP] Cyanogenmod 11 (4.4.4 - kitkat) for Wiko Stairway (mtk6589)

There is links to tutorials how to compile Android 4.4 to Cubot One

Also the is sources of MT6589.

But I can't see ant developer made ROM with android 4.4 for Cubot One.

Why ?

Thanks.
[Miscellaneous Android Development] bigrammy:
Because we are waiting for you to do it :cool:
[Miscellaneous Android Development] gintama_me:
bigrammy, I am not a developer and my PC has only 3 Gb of RAM.

And if this tutorials were for common people but not for developers I'd repeat a work. But I can't.
[Miscellaneous Android Development] nixmit:
I tried to apply this #643 update, but installation was aborted. Several others I tried to install from sdcard were aborted also.

Has anyone a solution for this problem?
[Miscellaneous Android Development] svgyula:
Greetings! Can anyone help with a ROM "Cubot one s" link? The phone will only start bootloop! no recovery! I need full flashtools ROM. The Phone ist MTK6582

Thank in advance!
[Miscellaneous Android Development] ramshi.faiz:
Hi...i need firm ware for K7-MB-V2.2..can u pls help me sir
[Miscellaneous Android Development] santos1911:
hi, i installed MIUI 4.08.29(JB 4.2.1) but the keyboard keeps crashing all the time.... even though i picked xperia keyboard. is there a fix for this? it is pretty damn annoying.

Google market cannot fetch data, even when i update it with a fresh apk via usb.

edit:

managed to solve the keyboard error:

i picked xperia keyboard and in language and input disabled text prediction and in android keyboard disabled everything that had a tick in the box.

so far no keyboard errors :)

now just have to figure out how to handle the google play market problem... i get the error [HR-01]

i thought it had to do something with google play services , so i tried to install the latest version but there was a parse error.

then i tried to install an earlier version and managed to install it, but as soon as the install was over it started crashing and google play market was still not working.

so currently i have to download everything from apkpure.com , transfer it to the phone via usb and install....

the even bigger problem is the internal memory. cubot one has about 8 GB of INTERNAL memory which is again (probably virtually) divided into internal memory of about 1,06 GB and external memory of about 5,96 GB.

under storage settings , no matter which i pick, external or internal storage for gallery , video , music, it doesn't work...

i cannot shoot pictures, video, download pictures or video from whatsapp, download ringtones etc because it is always saying that there is no sd card. how do i force it to accept that "virtual" sd card or even internal memory?
[Miscellaneous Android Development] santos1911:
is anyone in this thread alive :confused:

edit: i managed to get the storage working, but not permanently. i put in sd card from my phone into my wife's phone, shot some pictures, video, etc. removed the sd card, and checked if i got the same message. I DIDN'T! storage is still working, pictures and video are going under /storage/sdcard0/dcim/... ringtones are also available for download and i can finally access the "local" tab with default ringones. As i said, this is not a permanent solution, because as soon as i reboot the phone, the problem is back again. I believe it is all a matter of changing a few lines inside a single file (maybe vold.fstab? ), so i need someone to help or at least put me on the right track to do it myself.
[Miscellaneous Android Development] CVAngelo:
My preferred keyboard is the SwiftKey keyboard. It's the best on the market and never crashes. It simply works. But regardless of which keyboard you choose, make sure that you select it as the default keyboard AND UNSELECT any other keyboard that has a checkmark next to it.

This error often occurs with custom ROMs. It's extremely difficult to solve on custom ROM s but easier with stock ROM. Try this: Delete the data from the Google Play Services (you don't need to install the latest version as it auto updates to the latest version). Also delete data from Google Services Framework and also from Playstore. Make sure you have an open Internet connection. Now, reboot the phone. Open Play Store and it should ask you to accept terms and conditions. Do so. Close Play Store. Now wait several minutes till Play Store updates to latest version 6.0.5. Then try to download a small app like CPU Spy.

If you have a custom ROM, you may need to reinstall the ROM but then install the MINIMAL gapps for that version of Android. The minimal version may still give the HR-01 error, but it's easier to resolve by clearing the data of Services, Framework and Play as described earlier.

Some phones require that you have an external SD card in order for the phone to handle data properly. So keep one in your phone. Make sure it is larger than 2GB...for some reason, 2GB cards can be problematic in some phones.

You may have too much bloatware.

Root your phone, then download and install Busy Box X. Then install Uninstall Master and delete "system" apps that are not needed. For example, some phones/ROMs come with Facebook and a host of user apps (especially the Google apps like Maps, Gmail, Chrome etc) installed in the system partition. Delete them from the system partition and reinstall them as normal user apps.

The problem is that before an app can be stored on the SD card, a part of the app must reside in the reserved portion of internal storage. And if that reserved part in internal storage is full, then you will get an error saying that there is insufficient memory, even though you can see tons of internal and/or external memory remaining. Bloatware apps can cause that reserved portion of internal memory to be fully used up.

Also, check your internal SD card folders for one called Lost & Found, and another called Mtklog. Delete them. These are temporary unneeded files.

Finally, back up all your photos.

Then go to the Gallery app and wipe the data. It may also be a source of problems with the camera app's ability to save data even when tons of memory is available.

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

You cannot install an official update via OTA or sideload if you have a modified/custom kernel or recovery on your device. You must first flash the stock kernel and stock recovery back to the device. Doesn't matter if you're rooted. Then apply the official update. It should work. After you've updated, you can then reinstall your custom partitions. And you'll have to re-root as well.
[Miscellaneous Android Development] santos1911:
Bloatware? absolutely none. everything i installed after the rom are: whatsapp, root checker, root explorer, blackmart (since gapps is not working).

why on earth would i now go and buy an sd card if i have 8 freaking gigabytes of internal storage. which is recognized, but won't save on it unless i plug an sd card in and out of the phone.