yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] ovidiumatei23:
I tried to flash different ROMs with the new 0.8 cwm and with v0.8 firmware on my phone and as you said it cannot be done. I tried also to flash the 0.3 ROM as you said but the spflash tool gave me a 4032 error. I bought the phone about 2 months ago and it still bothers me that i cannot flash MIUI or JG4 or other ROMs. The only thing i was able to flash is the V0.8 update, because my phone came with v0.7. My friend has a phone with the mtk6589 1.2 processor and its much faster and smoother than my 1.5 turbo. How could i flash the older v0.3 firmware so i can flash MIUI or other roms?

Thanks

---------- Post added at 05:50 PM ---------- Previous post was at 05:37 PM ----------

Can u please tell me how did you restore the stock boot image?
[Miscellaneous Android Development] stari_alca:
Did you make a backup of your original firmware after you rooted it and installed CWM recovery?

This is what I did.

Rooted using framaroot. Used the 0.8 version of the CMW recovery image. Used Mobileuncle tools to flash that recovery image onto the phone.

Booted into recovery. Made a backup of, basically, stock rom.

After flashing Xplor Z it would not boot. So I did this:

Boot into recovery.

Go to BACKUP AND RESTORE

Go to ADVANCED RESTORE

Go to the appropriate backup folder - the name is the date and time of the backup

Choose restore boot

Confirmed YES I want to restore this.

It booted just fine after that.

So, again, have you made a complete backup while still on the stock firmware (0.7 in your case)?
[Miscellaneous Android Development] arqileing:
For changing boot.img there are two options. Option one: if you have your backup rom than you may restore only boot.img by going to cwm: -backup and restore/ advanced restore from internal sd (or external sd)/choose your backup/restore boot. option 2 before you install your custom rom you should extract to your computer or even to your phone and replace boot.img with the stock one that you can find to 0.8 rom. compress again as zip and install with cwm.

For your problem with sp flashing tool try to update sp flashing tool and drivers of your phone.

Sory for my english!
[Miscellaneous Android Development] ovidiumatei23:
I have several recoveries made for my cubot one so there is no problem there. I will try this and keep you posted. Thanks for helping

---------- Post added at 10:35 PM ---------- Previous post was at 10:01 PM ----------

With your help i now can install any rom meant for my Cubot one phone.

Thank you very much, u don't know what this means to me. Tomorrow i will give you all the likes possible
[Miscellaneous Android Development] gericom66:
Help i lost Imei when change recovery

Hello everyone I have a week cubot one mt6589 1.5 ghz, and mount the original firmware D1_V0.8_20140124_MJK, I used FRAMAROOT for rooting, but when I use mobiluncle to install the new recovery, reboot to lose the IMEI codes.

The recovery, in this case the CWM Touch 6.xxx back to me like that error can not mount the cache, the system etc.etc., You can help me.

thanks
[Miscellaneous Android Development] stari_alca:
Which recovery did you try to install with Mobileuncle?

There is a new version of the recovery image that works with 0.8 stock models.
[Miscellaneous Android Development] gericom66:
I have tried to install this cwm TOUCHRECOVERY in Version 6.0.4.4

Thanks to carliv
[Miscellaneous Android Development] stari_alca:
This is the recovery image you should use with Mobileuncle on a stock v0.8 Cubot One model:

http://xdaforums.com/attachment.php?attachmentid=2633416&d=1394968579

You should use SP Flash tools to flash the stock 0.8 firmware, then root, then install Mobileuncle and the correct recovery -- the one I am linking above. Yes, it is a touch recovery by carliv but its been adjusted for the 0.8 models.
[Miscellaneous Android Development] gericom66:
Ok thank you i tried......

Bye good night
[Miscellaneous Android Development] abell431:
Cubot one dead

Hi I was wondering if anybody could help me.

My cubit one was working fined and now it will not turn on. I cannot access recovery or anything. I have tried using a different battery but it has not help. I think I need to use SP tools but my PC will not recognise it so I am worried

Thank you very much
[Miscellaneous Android Development] stari_alca:
You need to install the proper drivers. Depends on your operating system -- but search and you will find many tutorials and links to specific drivers. What you need are MTK drivers for your version of Windows.
[Miscellaneous Android Development] gericom66:
Thanks for the help and the proper recovery, which now runs perfectly on the phone.

What do you advise me to install cooked rom or try?

Thank you so much for the help.
[Miscellaneous Android Development] stari_alca:
I have tried the latest MIUI and Xplore Z. But stock 0.8 is best for my needs.

Make backup and test a few ROMs to find what is best for you.
[Miscellaneous Android Development] gericom66:
Thank you, I read on some sites that mediatek will release updates for its products in KITKAT, has some other news about you or is it confirmed?
[Miscellaneous Android Development] paragraf:
pinout

Hello Guys!

I bought a new headphone with mic for my Cubot One but it's not working as it should. When I push the Mic's button it's louder, but the funcion button not works as it should. I can't pick up the phone, pause the music, etc.

I read after the problem and looks like te pinout is different on the Cubot from the most commonly used pinout. Does someone know how this pinout looks ? I'm curious if possible to make a converter for it to be able use properly the new headphone.
[Miscellaneous Android Development] stari_alca:
Have the exact problem. I tested 4-5 different types of headsets. Finally found a headset that came in the box with another MTK phone, Prestigio Duo 4322, that works properly with my Cubot. I couldn't find any solutions online so if you figure something out please tell us.
[Miscellaneous Android Development] gericom66:
when I do not use headphones, but I'll try some other brands. A question stari_alca, which launcher uses, because I have installed APEX and every time I reboot the phone, it loses the configuration of the widget.

I tried to make up the launcher and desktop but nothing to do, which launcher do you use?
[Miscellaneous Android Development] stari_alca:
I use the free version of Nova Launcher. Works great for me.
[Miscellaneous Android Development] gericom66:
Well I try it myself, thank you.
[Miscellaneous Android Development] paragraf:
solution on the headphone pinout problem

A friend of mine found the reason and also solution of the promblem.

The reason explained here: http://forums.androidcentral.com/samsung-galaxy-s3/189523-final-soultion-why-most-headsets-wont-work.html

The 2 pinout named CTIA and OMTP. And there are CTIA to OMTP converters (works both ways) on the market. Simple search for "CTIA to OMTP 3.5mm Adapter" on ebay and you will find a lot of converter around $5 (with shipping).
[Miscellaneous Android Development] ovidiumatei23:
Does anyone know where to get a soft silicone case? I hate the hard plastic case that came with the phone and i don't like the flip coves. Someone wrote that cubot sells them directly but i tried to contact them by email but with no succes. The email is cubot1001@gmail.com
[Miscellaneous Android Development] undacc:
Hi,

I'm looking for a working backup or working custom instalation incl. scatter file for use in sp flash tool.

I stuck in bootloop and can not enter recovery or factory mode.

According to the seller, its the 1,5Ghz Version.
[Miscellaneous Android Development] undacc:
OK. I found a solution.

The Stock ROM with this build # ist listed as Cubot One Turbo at Needroms. After many tries the tool flashes it to my phone.

[MENTION=1124043]Maximus1a[/MENTION]: I tried to flash your miui a second time, end up in bootloop. I think, it isn't working für the above mentioned chipset. Or it doesn't work for downgrade. Maybe you should point this out in the first post.
[Miscellaneous Android Development] ovidiumatei23:
Read post 484
[Miscellaneous Android Development] Mbariah:
Hi, am having a weird issue with my friend's Tronsmart TS7 8gb version mtk6589T(1.5 GHz)..Before you say wrong thread..i can assure you that it's the same phone as the cubot one since i have successfully flashed over 5 cubot one roms(stock and custom)..even from this thread..with no compatibility issues. In fact, it currently is running on a cubot one custom rom XPLOR S4_for_CUBOT ONE_port Legiondark_V4 and recovery.

Now there's a weird lag on the UI that is driving me nuts(was present on stock roms and all other roms i have tried)..Despite clocking at 1.5 GHz, the phone is a lot slower when moving about the UI than my Cubot GT99(1.2 Ghz mtk6589). I tried changing roms but the issue is still present..also Antutu is at 16490. I also have noticed that when benchmarking with nenamark v2..the phone manages only 32-33 fps on all roms..my cubot gt99 reaches 46.7 fps yet the powervr 544 is supposed to be clocked higher on mtk6589T.

Any suggestions?? also what fps are you getting on your cubot one on nenamark v2..(its an 11mb app)
[Miscellaneous Android Development] bigrammy:
Hi,

1, Get the latest most up to date Tronsmart Stock boot.img and uboot.img (lk.bin) or full firmware and flash to your phone.

2, use mtk droidtools to make you an unsecured boot.img using the latest boot.img and flash back to the phone.

3, now make a backup of the uboot and boot.img and save them as a pair.

4, now get my rom from HERE

5, swap the boot.img in the .zip with your own latest unsecured boot.img.

6, flash the rom and enjoy.

Reasoning: When you flash multiple roms update.zip's and spflashtool updates things can get out of whack where possible it is best to maintain your own uboot and boot.img as a pair because they are designed to work together. So unless you know that the custom rom is 100% exact same version as your firmware the boot and uboot maybe mismatched which can cause many little weird problems. :laugh:

Try it and see if things improve ;)
[Miscellaneous Android Development] tyetya:
recovery does not work

hi guys!

i really need your help! i tried to change the recovery on my new cubot one 8G, like it is written here. I rooted the phone, than i tried to load the Cubot-One_Touch_recovery_6.0.4.4.img to the phone with the MTK Droid Tools 2.5.3, but it does not work. it says everything is ok and asks if i want to reboot into recovery. If i say yes, then it goes to recovery, but i can't see anything but rainbow glitches for a few seconds. After this the whole screen switches to white. After ~20-30 seconds the phone reboots to the ROM. So the phone is functioning, but i can't enter the recovery.

I tried to change the recovery with mobileuncle tools too, but no luck.

Has anybody any ideas?
[Miscellaneous Android Development] tyetya:
some hope

i got a tip from a hungarian forum, i should get the Cwm_cobotOne.zip and "update" my recovery with it. unfortunately i can't find this file. is there maybe anybody, who can upload this file for me?
[Miscellaneous Android Development] gericom66:
No flash rom

Hello. I need help I installed the Carliv touch recovery 6.0.4.4 I tried to flash miui rom are both found on needrom that the Xperia rom, but even if I run all the wipe, for both the rom the phone freezes on the home screen. Can you help? Thanks

---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------

I have the cwm 6.0.0.4 by Carliv, you looking it? If yes I can you give you.

By
[Miscellaneous Android Development] tyetya:
cwm

thanks gericom,

but i lready got some help. some pals from another forum helped me out, they informed me, that since 2014.04, there is a new version of cubot one, and therefore these recoverys (

http://xdaforums.com/showpost.php?p=45286134&postcount=3

) does not working on my phone.

one guy ported me a new cwm recovery direct to my phone (from my original kernel files), since then the cwm recovery works fine on my phone.

unfortunately i wasn't able to use the miui roms... :(
[Miscellaneous Android Development] tyetya:
bluetooth issues with cubot one

hi guys!

i have a cubot one 1G / 8G, i run it with stock rom. i have an issue with the BT. I use it with several BT devices (car kit, wireless headset). Mediaplay works fine with both, but if i want to make a call, then almost allways (9 out of 10 times) the phone loses signal for a second, the call hangs up and it says that there is no signal, then the signal automatically comes back after 1-2 secs.

has anybody had the same issue? any ideas how to get rid of this failure?

thanks!
[Miscellaneous Android Development] mouk:
What Rom Version you are using?

Gesendet von meinem CUBOT ONE mit Tapatalk
[Miscellaneous Android Development] tyetya:
g800_cubot_d1_v1.3_2014_03_28_mjk
[Miscellaneous Android Development] Gotanius:
Hey!

I had the exact same problem. I changed the rom to the custom galaxy s 4 rom that is posted in this thread.

The exact issue I don't have anymore... However, If I make a call via my bluetooth carkit and 3G is on, people on the otherside can barely hear me. They hear a lot of static. If i disable 3G, the issue doesn't occur.

Hope this helps :)
[Miscellaneous Android Development] tyetya:
good to see, that there is a solution. :)

could you please tell me, which version of cubot one do you have? i got the new version (kernel: 3.4.5). Just because i tried to flash the latest miui rom, but its kernel doesn't compatible with the new version of the phone, so it ended up with bootloop. I would like to avoid the bootloop this time :)

thanks!
[Miscellaneous Android Development] babyboy3265:
Gents, my wife is having the cubot one 1.5ghz non turbo version, with the Jyiau ROM installed for a while.... She keeps running low on space and i thought to install the SD card swap file from the 1st page..

Before i do it ,are there any advices you have for me? Will there be any mess after installing it NON fresh?
[Miscellaneous Android Development] abanuelosh:
I am having an issue related to that...

Ithink so there is a new version of cubot one mt6589t...

I bought the Cubot One a month ago, and no one of the recoveries were supported, so i flashed the stock firmware V0.8 with sp flash tool intending to refresh the phone and brought back to factory state, but now i have an issue related to the LCD driver (maybe there is a new version of the IC), the phones works almost fine, recieve calls, i can connect via android screencast, mtk droid recognizes without problem, but the SCREEN is BLACK and backlighted. the original firmware was v1.3, the original backup was lost in a harddrive failure...

---------- Post added at 12:51 PM ---------- Previous post was at 12:46 PM ----------

Hello, i am interested in this version of firmware, i will be really grateful if you post the "mtk droid tool" backup of this version of the stock firmware. I suppose your cubot one was recently bought (since 2014.04), and is the mtk6589t version. Please help me bring back my cubot to life :o
[Miscellaneous Android Development] tyetya:
hi abanuelosh,

here are my "main" files from the backup. (i can't upload the whole backup, because it's 1,3 GB) I hope that you can "repair" your cubot with these files, if you need anything else, just write me! ;)

http://speedy.sh/cJswT/cubot-one-tyetya.zip

good luck mate!
[Miscellaneous Android Development] abanuelosh:
Thank you!!! but the issue remains...

Thank you for your help, I flashed the files without problem, I did some tests with the files, the phone boots, pushed with adb the build.prop, but the screen stills black and backlighted, i am thinking that will need the other .img and .bin files, and perhaps the nvram backup...

I still thinking if you would send me these files prepared for flash tool, please:

boot.img

EBR1

EBR2

lk.bin

logo.bin

MBR

MT6589_Android_scatter_emmc.txt

preloader.bin

recovery.img

secro.img

And the raw backup files:

nvram.bin

uboot.bin

You already sent me boot.img and recovery.img files, dont send system.img, will try to use the system.img of the current image tweaked with the new build.prop.

I will really be totally gratefull for your kind help!!!!
[Miscellaneous Android Development] arqileing:
You can flash a fresh copy room for your cubot one with sp flashing tool
[Miscellaneous Android Development] abanuelosh:
That is precisely the problem

The "fresh" firmware (V0.3 or V0.8 available in needrom) is not completely compatible with the newest version of cubot one released since april of 2014, the newest firmware is the v1.3 mjk, I lost my backup in a hard drive failure, the phone works almost completely with firmware v0.8, but the screen appear to have a different lcm driver than in the v1.3 firmware, then the screen appears black but backlighted, the screen is ok and there is no physical damage in it, the phone can receive calls, connect to the wi-fi, the hdspa+ network; those drivers are in the system.img but the lcm display driver perhaps is in the secro.bin, preloader.bin, uboot.bin or in the nvram. I think the problem is related to the driver because when the phone memory is scanned the "ERROR: NAND Flash was not detected" is related to the blackscreen. (http://xdaforums.com/showthread.php?t=1866962)

Thanks for your response :highfive:
[Miscellaneous Android Development] gericom66:
New Upgrade for CUBOT ONE?

I have a Cubot one bought two months ago and would like to know where to download the update for which you write.

thanks

g800_cubot_d1_v1.3_2014_03_28_mjk
[Miscellaneous Android Development] arqileing:
I think you have diferent kernel. Can you explain me what's your kernel?
[Miscellaneous Android Development] bigrammy:
Hi,

All Official Cubot ROM's are Here ;)

As for your problem I think this is your uboot also called lk.bin in most firmware upgrade packages nowadays.

You need to keep the uboot and boot.img as a matched pair because you can get these sort of problems if they are mis-matched

Ignore the NAND Flash error this happens on all my mtk6589 phones. :laugh:
[Miscellaneous Android Development] abanuelosh:
Thank is solved the problem thank to tyetya

Thanks for the advice regarding to the NAND flash issues. ;)

The problem seems to be regarding to the lcm driver in the newer cubot one turbo MTK6589T, this driver is somewhere in the uboot (or lk) or in the sec_ro, the lcm in the current roms available before 2014.04 is the 1-nt35590_mjk_kj, however the newest (since 2014.04) cubot one has the driver named 1-nt35521_jk, i think this is an un-documented change in the hardware, this latter driver is in the build G800_CUBOT_D1_V1.3_

20140328

_MJK; the "newest stock" firmware available in the internet is the v0.8, the build is G800_CUBOT_D1_V0.8_

20140124

_MJK, and the supposed update is the version V0.4, the buils is G800_CUBOT_D1_V0.4_20130807.

This flashable image is really hard to find, then i will work to cook a rooted and de-chinesed build G800_CUBOT_D1_V1.3_20140328_MJK, because all the available recoveries don't work, i will try to port a decent recovery. The MIUI fakeflash roms, don't work either.

---------- Post added at 09:37 PM ---------- Previous post was at 09:28 PM ----------

The kernel version are the same, but the build date is different, the problem seems to be a newer display hardware, not documented, these displays use different drivers, 1-nt35590_mjk_kj is previous to april 2014, probably the newer kernel build has been compiled against a different driver (1-nt35521_jk).
[Miscellaneous Android Development] bigrammy:
Thanks for the info bro :good:

I guess there will be a lot of confusion coming our way now. :( People will now be flashing the wrong versions and complaining when their screen and recoveries will not work. :laugh:

Also it means that Cubot will only release update's for the latest version of the phone which has your screen :crying:
[Miscellaneous Android Development] luki2202:
Hi,

I have a problem with my cubot one. It's on stock rom without root.

Yesterday i was using it normally (turned the screen off then powered it on again)

but the screen is now black (nothing appears on the screen but led's are working).

I can unlock it (i hear the sound) and i hear normal booting sound-theme.

Do anyone have any idea what can i do?
[Miscellaneous Android Development] Domcek:
[MENTION=3924647]bigrammy[/MENTION]

If I try firmware upgrade, result is in attach.
[Miscellaneous Android Development] Gotanius:
Is there any sight on a android 4.3 based custom rom for the Cubot one?

I have been googling for a while and couldn't find one :(

The reason I ask is that i need AVRCP 1.3 vor my bluetooth carkit :)

Any ideas?
[Miscellaneous Android Development] Maximus1a:
in short words.... maybe.

kitkat sources are available for another mtk6589 device but our phone has different drivers. until these drivers are kompatible to kitkat you will not be able to build a fully working android 4.3 or 4.4.
[Miscellaneous Android Development] Gotanius:
Hmm I indeed read something of the sort. Could drivers be 'built' or would the manufacturer need to step in?

Would there be another way to get avrcp 1.3 on the older android rom for cubot one?
[Miscellaneous Android Development] Maximus1a:
mtk does not have a clue what open source is or does not want others see what patents the breake. ;)

so only mtk can build drivers, or a smart guy has to programm them from scratch.
[Miscellaneous Android Development] Gotanius:
Haha I figured as much, that is too bad tho' :(
[Miscellaneous Android Development] abell431:
Hi my cubot one will not turn on or even boot to recovery. What drivers do I need to install on my computer? how can I fix my phone :(
[Miscellaneous Android Development] abell431:
please help me
[Miscellaneous Android Development] Maximus1a:
a little less information from your side. what have you done before your phone did that?

what version of this phone you have?

one (6589)?

one (6589t)?

one S (6582)?
[Miscellaneous Android Development] Rafaelia:
Using MIUI 4.1.19, is there any way to make the camera 13 megapixels and increase the in call volume?
[Miscellaneous Android Development] abell431:
sorry it is the 6589

I had installed a custom rom(cannot remember exactly which one) and it was working fine then one day it just would not turn on. I tried changing batteries etc. Sometimes my old computer would make a noise when i plugged it it but not my new computer :(

help would be appreciated!
[Miscellaneous Android Development] Ergina95:
:(

files not found? :(
[Miscellaneous Android Development] Maximus1a:
3.11.15 and 3.12.13 are up. the other files where deleted by dev-host. someone may have abused them or...... what ever.
[Miscellaneous Android Development] Ergina95:
no other link for MIUI 3.8.16 (JB 4.2.2) ? :confused:
[Miscellaneous Android Development] Maximus1a:
the old versions are not so good, better use the newer ones.
[Miscellaneous Android Development] alexmbra:
Auntutu gives me 17010 :) So, thanks for this room! But so far, I just found two problems. One is the one that you mentioned about the "default storage location", and the other is GPS does not lock at all with this room. :(
[Miscellaneous Android Development] alexmbra:
Hi androidia.

Just finished trying your room. Just like bigrammy's room, GPS does not work with yours also. But at least, it enables it, but it couldn't get a location even with WIFI Location enabled. :( But with your room Auntutu gives me 16793.
[Miscellaneous Android Development] bigrammy:
Hi,

The default storage can be set by selecting Setting/Device/Storage/ Then Select Phone Storage all System Apps will then update without issue. :good: You can always use Link2sd app to move apps to the SDcard if you need the space.

As for the GPS issue make sure you have done a full wipe from the recovery before installing the ROM Wipe Data, Cache, and Delvik Cache

Flash the ROM then wipe again before booting back into the system.

If that does not fix things flash your own stock boot.img wipe again then re-boot this usually fixes any issues. ;)