Database Info

Xoom root and bootloader unlock

I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).

wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?

Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.

RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.

Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?

llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted

TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)

llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?

TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me

I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?

madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.

Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!

Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?

do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.

factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!

madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5

sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).

madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge

Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!

madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[UTIL][WIN][MT65xx] MTK Droid Root & Tools | MediaTek Android Smartphone

This post was created originally by rua1 and transferred to new owner as old maintainer rua1 is no longer active.
Scope of the thread
The scope of this thread is ONLY about to discuss how to use MTKDroid.
IS NOT in the scope post not about MTKdroid, like ex. how to create recovery (except the CWM create by MTKDroid) or root the device (except procedure integrate in MTKDroid)
What's MTKDroid
MTKDroid is an application created by rua1 for Android device based on Mediatek CPU MT65xx (not other CPU type) and Android up to 4.4..
CPU/Android OS version/ROM chunk size supported
Mediatek CPU supported
IT'S GENERALLY COMPATIBLE with CPU Mediatek MT65xx (ex. MT6582/MT6589/MT6592) and Android up to Android 4.4.x (not higher)
IT' COMPATIBLE with old CPU version (MT6582/MT6589/MT6592).
Could be not compatible with recent CU MT65xx (like MT6580)
IS NOT COMPATICLE with new CPU like Mediatek MT67xx (MT6732/MT6752/MT67537etc).
IS NOT COMPATIBLE with Android OS 5.0 and higher (5.0/5.1/6.0/7.0)
IS NOT COMPATICLE with CPU not Mediatek.
Android OS versione supported
MTKdroid is COMPATIBLE with Android OS version up to 4.4
MTKdroid is NOT COMPATIBLE with Android OS version 5.x (LP) and higher like 6,.0 (MM), 7.0 (Nougat), etc
ROM chunk size supported
MTKdroid is COMPATIBLE with ROm chink size = 512 bytes/sector
MTKdroid is NOT COMPATIBLE with ROM chunk size > 512 bytes/sector (ex. 2048 bytes/sector)
Before to start
Please note that you use program at your own risk!!!!
ATTENTION! It is possible to brick the device!!! - Please read carefully here
Check if you can, to make a backup of your ROM or to have a full backup of you ROM.
Check in the Android device if DEVELOPER OPTIONS is available into SETTINGS menu.
If DEVELOPER OPTIONS is not available. please enable it selecting SETTINGS -> INFO ABOUT THE DEVICE -> Click several times on BUILD lines.
It will appear a popup DEVELOPER OPTIONS enabled.
Check that in the device SETTINGS -> DEVELOPER OPTIONS -> USB DEBUG is enabled
ADB device drivers are already installed, and in the Windows DEVICE MANGER there shouldn't be unknown devices at connection of switched-on phone.
ADB drivers can get here
Please check here an example of USB Debug menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MTKDroid original russian thread - use Google translate
Guide in English
- If your phone not rooted using the ROOT button
- Problems and errors when using SP Flash Tool
- Backup ROM and make backup flashable in SP Flashtool
- How to install CWM on some rooted MTK devices
Program history/changelog
- MTKDroid v. 2.4.3
- MTKdroid v. 2.4.4 / v. 2.4.5 - Info
- MTKDroid v. 2.4.6 - Info
- MTKDroid v. 2.4.7 - Info
- MTKDroid v. 2.4.8 - Info
- MTKDRoid v. 2.5.1 - Info
Download
MTKDRoid v. 2.5.3 mod by bovirus (Mega)
Post all details
Post all details about the device that you can like
brand/model/CPU/ROM size/Flash size/Android version/ROM version/ROM date
If you have problems or errors, please attach at this thread the log.txt file available in MTKDroidTools folder![/B]
Language files
Note: the files are already included in last versions. No need to download and add them.
- Spanish language (Spanish.lang)
- Czech language (Czech.lang)
- Italian language (Italian.lang)
If you want to add new language, please translate English version and post the new language into the thread.
If you find errors about language pelase post the report in the thread.
..

- Additional options for newwer MTK chipset
Sonme trick for newwer chisper and Android version
Temporary root on Mediatek
GUIDE - How to
This guide was created originally by rua1 and transferred to new owner as old maintainer rua1 is no longer active.
- Make a ROM backup using Flashtool and ReadBack
- make the CWM recovery
- install SuperUser (get root)
- etc..
If your phone cannot rooted using the ROOT button.
1. Make scatter by means of MTKDroidTools
Scatter is the text file with addresses of the blocks, necessary for the SP FlashTool program.
After creation of scatter don't close the main window of the program!
Otherwise once again it is necessary to turn on phone.
2. In SP FlashTool choose this scatter and go on the Read Back tab
3. Choose path and a ROM file name
Click on Add button. Double click of a mouse on the appeared line. Choose a file name, the name has to begin with ROM_ as offers FlashTool! Remember path and the name of ROM_ file.
4. Determine the ROM_ size
Type has to stand in HEX. In the field of Start Address it is necessary to write down 0x000000. In the field of Length we copy from scatter the address of the block following after RECOVERY or the address of other block for fuller backup. For phones with type of the blocks EXT4 it is the cache block address. The number in the Hex format has to begin with 0x
5 . Choose Read Page Only on yaffs2 type blocks phones
In FlashTool choose Read Page Only in the field of Read Method. If this field isn't present, the window with this question can emerge, too we choose Page Only. On phones with EXT4 blocks it doesn't get out (as a rule).
6. Read Back ROM_
Click on Read Back button and connect the switched-off phone to PC. Here the options depending on a concrete phone are possible. Maybe it is necessary to press at the same time with connect of a cable the camera or volume buttons. Experiment and study work with FlashTool in threads with similar phones! On some MT6573 models, for example on B63, it can't be executed with any combinations and only testpoint need!
7. Prepare files for FlashTool and make CWM
If everything passed without errorss, we open the MTK Droid Root & Tools window which we left on 1th step. If for some reason the window isn't present, it is necessary to turn on phone and to connect it to the program. Click on To process file ROM_ from FlashTool button and choose the ROM_* file saved on the 6th step. At successful unpacking rom it will be offered to choose CWM from similar phone. Chosen CWM it is checked on compliance to the connected phone and if ok, the CWM is created.
Starting with v2.4.0 CWM it is made automatically and the file from similar phone shouldn't be looked for any more!
Аttention! Yaffs2 type blocks from this backup can't be Downloaded to phone, they aren't correct!
Use backup on 9th step if phone have yaffs2 type blocks!
8. Download new CWM to the phone
Start FlashTool, choose scatter in the folder created on the 7th step. Remove marks from all blocks! Click on RECOVERY and we choose the file CWM in the same folder which was created on the 7th step. Click Download and connect a cable to PC (phone has to be switched off) and expect the end of process.
DANGEROUS! On this step the CWM recovery block has to be marked only!
Also it is necessary to use only the Download button and not to use at all the Firmware Upgrade button!
9. Make backup, install SuperUser etc
Start device in CWM mode, connect to MTK Droid Root & Tools, go on the tab root, backup, recovery and, pressing on this tab the necessary buttons, we do:
- backup! ! ! (if in phone there is yaffs2 type blocks, do here surely, they received with readBack on 7th step aren't correct)
- install superuser (often mean "get root" under it)
- and other if need
Never needlessly flash/download preloader and DSP_BL blocks! It is always dangerous!
On some models of phones (for example Alcatel) you will have a brick even if you download these blocks read from phone which you own!
Always remove from them marks in SPFT!

I'm very glad to see you here! Welcome to XDA and thanks once again for your great tool. :highfive:

bgcngm said:
I'm very glad to see you here! Welcome to XDA and thanks once again for your great tool.
Click to expand...
Click to collapse
Thanks, long ago I wanted to open an English thread here... eh, study English better my sonny, mother spoke to me

I just wanted to say thank you to both of you guys Rua1 and Bgcngm (you too Yuweng), I couldn't have completed my project without your expert knowledge of MTK devices. You are awesome!

Big THANKS for creating MTK Droid Tools man!
One question about the backup feature of the tool. Maybe I just haven't tried it but, I understand you need to use the built-in Rooting tool of the program before creating a backup. What if my device is already rooted (without using the built-in rooting tool), how can I use the backup feature? So far, all the tutorials I've seen using the backup has rooted the device using the built-in rooting.
Thanks again!

You don't need to root your phone using the tool just to have access to the backup feature. Once phone is rooted (and insecure adb support enabled), backup button will be clickable.

OK Thanks man. I have to check on that again. Last time I tried it, the backup button is grayed-out.
O.T. also thanks to your CWM 6.0.2.8 for MTK. More Power!
bgcngm said:
You don't need to root your phone using the tool just to have access to the backup feature. Once phone is rooted (and insecure adb support enabled), backup button will be clickable.
Click to expand...
Click to collapse

nerbiyoso said:
Last time I tried it, the backup button is grayed-out.
Click to expand...
Click to collapse
Button is greyed-out when phone is not rooted and/or an unsecure adb connection is not established.
If you already have a CWM-based recovery you can also boot into recovery mode, connect the phone to the computer and then use MTK Droid Root & Tools to create the backup. That will surely work because normally recovery images are unsecured.

nerbiyoso said:
What if my device is already rooted
Click to expand...
Click to collapse
It means that on phone superuser is installed, in this case connection indicator in bottom left corner of program has yellow color. root shell is necessary for possibility of a backup. If to press the ROOT button, temporary root shell open and it will be possible to make backup
... or following:
bgcngm said:
If you already have a CWM-based recovery you can also boot into recovery mode
Click to expand...
Click to collapse

Problems and errors when using SP Flash Tool
Link on this subject in Russian
Modes of the virtual COM ports
In case of problems in operation with SPFT it is useful to listen to a sound on PC and to open a Device Manager. The sound signals about connection and switch-off of devices and the Device Manager shows a mode of the virtual port and information on drivers. If with drivers everything is all right, devices appear in the section Ports (COM & LPT) and the icon of the device shan't be marked by exclamation point ! in a yellow surrounding.
Modes of the VCOM:
BOOTROM (in device manager show as MTK USB Port with pid=003) . For connection in this mode can it is required :
to use press of some phone buttons (photo, volume up or down ) at the same time with connection of a cable to PC (phone shall be switched off)
or to use OTG adapter
or, if it didn't turn out 1 and 2, use a test point.
PRELOADER (...MediaTek USB VCOM Port with pid=2000 ) This port appears for only some seconds in case of connection of switched-off phone to PC
DA_HIGHSPEED (...MediaTek DA USB VCOM Port with pid=2001)This port can appear after phone at first will be connected in the PRELOADER or BOOTROM mode.
How to swith off DA Download All mode
Sometimes DA Download All mode switching off helps not to have errors with MTD type a flash. In the last FT versions it can't be made of the menu, it is necessary to change the platform.xml file. It is necessary to change in section of your platform usb_download_support and da_dl_all_support keys with "true" to "false"
After these changes it is necessary to connect a cable to PC, having waited the ends of counting.
ERRORS:
(2005) S_BROM_CMD_STARTCMD_FAIL often there is on phones with MTD type a flash.
During Downloading preloader or dsp_bl aren't marked. To use the suitable version of SPFT or to switch off the DA download All mode.
During Downloading preloader or dsp_bl are marked. Not mark these blocks! Or connect phone in the BOOTROM mode if it is necessary to Download them.
During reading, formatting or ROM-RAM testing. Сonnect phone in the BOOTROM mode.
(8038) SP FLASH TOOL ERROR here
To be continued ... or not to be

reserved for guide

Thanks for the tool, i tried this tool to root MicroMax A116 HD device, but no luck.
here is the log file as requested : http://pastebin.com/AD3GnYve

eagledipesh said:
but no luck
Click to expand...
Click to collapse
If kernel 3.4.x, ROM need to read from phone using SP FlashTool and to make cwm recovery. Guide in Russian here
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
It has screenshots that will help you to understand. In plans at first to make this guide in English

rua1 said:
If kernel 3.4.x, ROM need to read from phone using SP FlashTool and to make cwm recovery
Click to expand...
Click to collapse
Using builder.clockworkmod. com I was able to create recovery, but the recovery.fstab doesn't has mediatek related info.
I have dump of stock rom as well.
If i can share the recovery.img with you, would you be able to help me.
Sent from my Micromax A116 using xda app-developers app

eagledipesh said:
I have dump of stock rom as well.
Click to expand...
Click to collapse
it is good, but it is even better to have blocks read from the phone
eagledipesh said:
If i can share the recovery.img with you, would you be able to help me.
Click to expand...
Click to collapse
I will try to help, give link to all rom, I want to look at ROM MT6589. In log there was no information that is MT6589, and on the program screen it was? Probably it is necessary to change a code of the program for MT6589 support

rua1, only you can help me but unfortunately my English is quite poor so I don't know what exactly to do. The only think that I have done correctly is the installation from the drivers. I have a Lenovo A60+ ,s319 and I brick it. I have try a lot of roms but the mobile is still brick. Some photos about my mobile maybe help you.
http://imageshack.us/photo/my-images/526/dsc01097t.jpg/
http://imageshack.us/photo/my-images/547/dsc01089web.jpg/
http://imageshack.us/photo/my-images/341/dsc01091web.jpg/

@tsitadim
Sorry, here not unbrick thread. Using DroidTools at once backup all blocks from phone was necessary, not all ROM from the Internet are compatible to phone since at the identical names hardware in phones can differ.

hello again i've successfully backed-up while the phone is in cwm recovery. thanks! :good:
@rua
the version of the tool i have is 2.2.8. is this the latest version? it might be best if you can share the main download page so everyone can have the latest version.
this is a very useful tool that every mt65** owners should have in conjunction with mtk's spflashtool.

The latest version is 2.3.8. Just read the OP, it's all there. Even the link to the original thread on Russian forum.

[DISCUSSION][GUIDE][PORT][ROM] Alcatel One Touch 4030 S'Pop/Glory 2 Development

This thread is for discussion for the development of this device. All interested devs are very welcome to join and help.
I started working on this device since I got it day 1 on March 11, 2013. Slowly, I progressed to every step in learning more about this device. Since then, many have joined finding ways to make this device better.
UPDATE:
This thread is old and very few to none uses this device anymore. I will leave this thread here for your reference.
All of the developments of this device will still be posted here so always keep in touch with this thread for great news.
Cheers! :good:

Unbrick theory...
trying the one touch upgrade utility. it wipes all data in phone and installs a fresh and latest ROM for the device. i guess this will also fix a bricked device somehow.
after this i will try to root it again using MTK tools and ap flash tools with a different idea in my mind... hope it works this time...
[EDIT] UNBRICK METHOD CONFIRMED WORKING!!!

One touch Upgrade
Hello there I'm a total noob in rooting and unlocking bootloads. I just got the same phone as my first android phone and wondered how to root it and I end up here. Now I'm asking how did you get the one touch upgrade software. I've searched the whole alcatel website but I keep getting on the FAQ page. Would you be so kind to put up the link for the software because I kinda bricked my phone here. I was also wondering what speed did you use during your Bin4ry script root attempt? Normal or Special? Keep doing a good job. Thanks for having the time to look for ways to root this phone.

sabinbp said:
Hello there I'm a total noob in rooting and unlocking bootloads. I just got the same phone as my first android phone and wondered how to root it and I end up here. Now I'm asking how did you get the one touch upgrade software. I've searched the whole alcatel website but I keep getting on the FAQ page. Would you be so kind to put up the link for the software because I kinda bricked my phone here. I was also wondering what speed did you use during your Bin4ry script root attempt? Normal or Special? Keep doing a good job. Thanks for having the time to look for ways to root this phone.
Click to expand...
Click to collapse
I tried the normal mode as Bin4ry said that the others might brick the phone it it wasn't the right model. did you brick it using the srcipt? any way. still trying to root it and finding help from rua1 that has a great knowledge in MTK phones...
here's the link of the upgrade utiliuty... just install it and choose alcatel 4030 (if your phone is s'pop) then power of the phone remove the battery and follow the instructions on PC and wait till it says plug the phone while powered off.. plug the usb (without battery) then wait for it to detect the device. when it loads, put the battery back and wait for it to download the firmware.. it will take hours to download it.. it's about 2+gigs... good luck on unbricking.. hope it works...

Phone unbricked
Many thanks for the software. My phone is now back to stock rom. for the Bin4ry I also tried Normal because I thought it was for tabs only. So MTK is the only course of action? Any news on fixing the 2 point horizontal bug? and the alcatel FAQ says there's this TCL calibration that you can activate to you know "calibrate" the touch screen. Do you also get the problem where in the stock alarm app alarms but you can't dismiss it ( I set it to crazy mode ) where you need to press 3 buttons to dismiss but still won't stop I really need to pull the battery out. Help please Thanks in advance.

sabinbp said:
Many thanks for the software. My phone is now back to stock rom. for the Bin4ry I also tried Normal because I thought it was for tabs only. So MTK is the only course of action? Any news on fixing the 2 point horizontal bug? and the alcatel FAQ says there's this TCL calibration that you can activate to you know "calibrate" the touch screen. Do you also get the problem where in the stock alarm app alarms but you can't dismiss it ( I set it to crazy mode ) where you need to press 3 buttons to dismiss but still won't stop I really need to pull the battery out. Help please Thanks in advance.
Click to expand...
Click to collapse
Great. So my theory really worked. Glad you unbricked it. I'm getting closer to rooting it. Just having problems flashing the cwm. Ones I managed to flash it, rooting may be successful. I use Mtk tools and flash tools and get help from rua1. Didn't use my alarm before so i'm not sure about the bug. Maybe you don't have to set it in crazy mode..

I tried to set the alarm in crazy mode and everything works fine. Just dismiss, unlock, and tap the three buttons with numbers and your done..

Rooted, finally!!
I finally rooted the alcatel spop. I will make a guide maybe later how I did it...

[GUIDE]How to flash CWM recovery and root Alcatel One Touch S'POP 4030
How to flash CWM recovery and root Alcatel One Touch S'POP 4030X(Glory 2)
Disclaimer: Your warranty is now void. You do this in your own risk. I do not take any responsibility to your device. This will definitely brick your device which is normal but follow the right instructions to make it work again.
Credits: This is tuts would not be possible without the help from the creator of MTKdroid tools, rua1 from XDA Developers. Thank the guy for his wonderful tool. If you wanna know how I did it, go to his thread right here. I also wanna acknowledge The Solutor and rimmon1971's efforts for porting the TWRP to our device. You can find The Solutor's work here.
Requirements:
1. A windows based PC
2. MTK Droid Root & Tools & SP Flash Tool
3. Universal ADB driver
4. One Touch Upgrade S
5. Root script
6. Patience
7. Most important! Use your brain!
Important!
To make this work without errors, don't use other drivers available in the web. Just install One Touch Upgrade S first. It will install the USB VCOM preloader driver. It will be needed by the SPFT to detect the phone. Use the provided ADB driver for the MT65xx_android_phone. If ever you get stucked in an error and your device wont boot anymore, just use One Touch Upgrade and your phone will be as good as new...
Guide: CWM/TWRP recovery
1. Download MTK Droid Root & Tools & SP Flash Tools, ADB Drivers, One Touch Upgrade S, and the Root script. Extract them anywhere in your computer.
2.Install ADB driver.This step is now optional to get adb working. You can now skip to step 5 if you just want to get rooted with CWM/TWRP recovery installed.. In your phone, go to Settings>Development. Set to on and check USB debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Connect device to PC. Driver will fail to install (thats normal). Install UniversalAdbDriverSetup6.msi
Note: in Windows 8, this will pop-up. do this:
4. After installing the Universal ADB driver, go to device manager of your computer. Follow the images as descirbed.
ADB commands should work now (if you have ADB installed) and you won't have any problems about MTK droid tool not detecting phone.
5. Be sure that you have already installed One Touch Upgrade S before this step. Open SP Flash tool and select the scatter file by clicking on the Scatter-loading button.
6. UNCHECK BOOT and leave RECOVERY checked. Disregard what is on the photo. There's are reports that the latest firmwares are incompatible with the uploaded patched boot.img.
Note: By default, the CWM recovery will be selected in the SP Flash tool. If you want the fully working TWRP-recovery (I recomment this because CWM recovery is not fully functional), just click RECOVERY and replace it with this file.
7. Click Download button. Click yes on the download warning. Turn off phone, remove battery and connect the phone (without battery) and wait until SP Flash tool detects the phone and watch as it flash the image.
8. If everything passes without errors, unplug the phone, reinsert battery and boot to recovery by pressing power + volume up.
9. You should boot in CWM/TWRP recovery. We are ready to flash the Superuser app to gain root.
Guide: Superuser
You can use mtk droid root and tools here. Just plug in phone to pc while still in CWM recovery. Run mtk tools, wait to detect phone, click superuser, then build.prop, then delete china. Your done. Or use the guide below if you have problems with it.
Using CWM recovery to flash superSU
1. While still on CWM recovery, plug the phone into PC again.
2. Navigate using volume up and down buttons. Press Power button to select and Back soft key to go back.
3. Select mounts and storage>mount USB storage.
4. Copy the root-glory-2-4030E.zip to your sdcard.
5. After copying, select unmount and go back.
6. Select install zip from sdcard>choose zip from sdcard>root-glory-2-4030E.zip and select yes - Install root-glory-2-4030E.zip
7. It will flash the app to the system including all needed binaries. I also included the fix-permissions banary which is missing from the ROM.
8. Reboot the phone and wait. It will boot normally and no data will be lost. You will see superuser app in your app drawer. You are now rooted!:thumbsup:
Using TWRP recovery to flash superSU
1. While still on TWRP recovery,Connect the device to PC.
2. Tap mount in the screen then Mount USB storage.
3. Copy the root-glory-2-4030E.zip to your sdcard.
4. Press back on your device softkeys.
5. Tap install and select root-glory-2-4030E.zip
6. Wipe to confirm flash.
7. Reboot>System.
8 You're done.
Screenshots:
Guide to Unroot
Requirements:
1. Windows Based PC
2. SP flash tool (included in OT-4030 ROOT&CWM RECOVERY)
3. Stock recovery.img
4. Unroot script (Unroot-glory-4030E.zip)
Urooting
1. Copy Unroot-glory-4030E.zip to the root of sdcard.
2. Reboot to CWM recovery.
3. Select install zip from sdcard>choose zip from sdcard>Unroot-glory-4030E.zip and select yes - Install Unroot-glory-4030E.zip
4. On your PC, Open SP flashtool and select the scatterfile.
5. Remove check on BOOTIMG and click RECOVERY and select the stock recovery.img. Click download button and disregard download warning by clicking yes.
6.Connect the phone to pc without battery. After the download finished dialog, your done!
Links:
OT-4030 ROOT&CWM RECOVERY
Universal ADB driver
One Touch Upgrade S
Root script
Unroot script
Stock recovery.img
Mirror to all files
TWRP-recovery

I get this error after #3 of CWM recovery installation:

warfab said:
I get this error after #3 of CWM recovery installation:
Click to expand...
Click to collapse
Please attach log...

cyberangel22k said:
Please attach log...
Click to expand...
Click to collapse
Here are my logs...

Guide updated!
added some more steps for error 4050...

Anyone still getting errors, I will help today. you can send a PM on my personal G+ so I can answer quickly to your concerns...

boot_logo changed!
tried to change the boot logo and it worked! thanks to balamu96m for his guide.
This is my new boot logo

bootanimation problem!
I changed my bootanimation and tried if it works using these commands which i normally do with my past android devices.
Code:
adb shell bootanimation
the animation works fine but when i hit:
Code:
adb reboot
the animation showed was just android mask or android shine which shows when you don't have bootanimation.zip inside /data/local or /system/media. it's like a default bootanimation.
so once I booted, I tried again
Code:
adb shell bootanimation
the bootanimation works but when I reboot, it's back to default.
I tried replacing back the original bootanimation.zip but it still the defaut bootanimation. It's very weird. I haven't encountered this before...

cyberangel22k said:
Anyone still getting errors, I will help today. you can send a PM on my personal G+ so I can answer quickly to your concerns...
Click to expand...
Click to collapse
Me and many others are still waiting for your help at symbianize...

can't access symbianize since saturday
Dito muna kayo magpost ng mga tanong.. humihingi din ako ng tulong kay rua1 re: sa error 4050.

fixed!
cyberangel22k said:
I changed my bootanimation and tried if it works using these commands which i normally do with my past android devices.
Code:
adb shell bootanimation
the animation works fine but when i hit:
Code:
adb reboot
the animation showed was just android mask or android shine which shows when you don't have bootanimation.zip inside /data/local or /system/media. it's like a default bootanimation.
so once I booted, I tried again
Code:
adb shell bootanimation
the bootanimation works but when I reboot, it's back to default.
I tried replacing back the original bootanimation.zip but it still the defaut bootanimation. It's very weird. I haven't encountered this before...
Click to expand...
Click to collapse
Found out the cause of this issue. The stock ROM has no fix_permissions binary. So I pushed the binary and tried to fix perm again and now custom bootanimation.zip works!

4050 fix
to get past the 4050 error update the SPFlash Tool to this one http://forum.xda-developers.com/showthread.php?t=1982576
To those having problems with MTKDroid not detecting their phone download and install PDANet for Windows (any version would suffice)
just rooted my phone \^0^/

[SUPPORT] Star S9500

If you are interested in this phone, you can found it here:
http://www.geekbuying.com/item/Star-...ey-316069.html
This thread is ONLY for support of the Star S9500!
The Review topic is here:
http://forum.xda-developers.com/showthread.php?t=2458161
Support thread for Star S9500​
Topics:
Essential tools;
Installing drivers
How to ROOT;
How to remove China Apps;
How to change screen's DPI;
How to install CWM;
How to make a backup;
How to flash with stock ROM;
Solving Messages app BUG (tomorrow I will post);
Solving any GPS issues (tomorrow I will post);
Changing the Launcher (tomorrow I will post);
Changing the Resolution up to 960p (tomorrow I will post).
Essential tools​
Here is a list with download links for some indispensable tools:
Notepad++
Drivers
MTKDroidTools
SP Flash Tool v3.1312.0.139
17/05/2013 Official Stock ROM
Installing Drivers
Preloader​
We will start with the Preloader driver, which is the trouble one.
First of all, shutdown the Phone.
Go to the Start Menu, right click in the Computer, and click Manage. Then go to the Device Manager.
Now you need to be quick! Connect the Phone to the computer via USB cable, and when appears MT65xx Preloader as unknown driver, right click in the device, Update Device, select the second option, select the folder mt65xx+preloader+drive that you downloaded and check the Include Subfolders option. Now let it install. Once installed, it will disappear, that's the reason that I said to be quick. The Preloader disconnects when the device is not in use and goes to charging mode.
Now you can turn on the device.
ADB Driver​
This is the easy one. Connect the phone in debugging mode, and in the Device Manager it will appear another driver to install.
This time you only need to select the MTK_USB_ Driver folder and it will install!
How to ROOT​
Download the MTKDroidTools which is in the Essential tools section, create a folder and extract the files.
If the drivers are installed and the device is in debugging mode, it will appear a green block at bottom left side like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to root, backup, recovery section, then click on SuperUser option. Click on YES to every option that will show up. You can select SuperSU app or the SuperUser app. I selected the SuperSU. Now click on Reboot at bottom right corner
Now you have your device rooted!
How to remove China Apps​
In the same section as in the ROOT tutorial, you this time click in Delete china.
How to change the screen's DPI
Preparing the scenary​
This gives a better look to the screen and it will look like Galaxy S4.
I changed the DPI because of the 240 DPI to 480x854 screen is so huge that hurts my eyes, and I have so small space to the apps!
We will prepare the work to you don't manually edit anymore the build.prop file, just this time.
So, lets begin. You need ROOT to do this!
Open the Root Explorer, go to the system folder, keep the finger at the build.prop file and select Copy.
Now go back to the root (/), go to the sdcard folder and select Paste.
Now connect the phone to the Computer and enable the USB file transfer.
Go to the phone internal memory by your Computer, and edit the build.prop file with Notepad++ to preserve the Unix Style of the text. Go to the end and add the following line:
Code:
ro.sf.lcd_density=240
Save the file. We have set the DPI to 240, but we will change it later in an easier way.
Now let's put the file back to the phone.
Go to Root Explorer and go to the /sdcard directory. Now press the build.prop file and click the Move option. Go back to root, go to the system folder, click in Mount R/W and click in Paste. Overwrite the file.
Changing the DPI​
Now we can do the trick with the MTKDroidTools.
Go to MtkDroidTools folder, and edit the build_prop_replace.txt file.
It must have this code inside:
Code:
ro.sf.lcd_density=240
You can change to a DPI between the 120 and 320 I think. Higher the DPI, higher the icons, less space for them.
You can calculate here the right DPI for your screen:
http://pxcalc.com/
Insert the data just like I did:
Seems like the right DPI to the screen is 195 DPI.
You can test this inserting the 1080x1920 resolution with 5 inch. If it gives us 440 DPI, that is the correct DPI from Galaxy S4 specs from GSMArena.
Now change the 240 value to 195:
Save the file and go to MTKDroidTools.
Go to the root, backup, recovery section and click in build.prop option.
Then click Reboot to reboot the device.
Compare here the difference between 240 DPI (left) and 195 DPI (right) screen:
​
Now when you want to change DPI you only need to do this steps.
How to install CWM​
To install CWM on the phone, open the MTKDroidTools and go to the root, backup, recovery section.
Click on To use boot from phone and click the Recovery and Boot button.
Now click Yes to every option.
Now you can access to CWM recovery by pressing Volume Up + Home + Power, and the Volume Down + Home + Power stock recovery is still working.
How to make a backup​
To backup you whole ROM, open the MTKDroidTools and go to the root, backup, recovery section.
If you want to backup your personal data to a personal backup, check the Backup userdata and cache box (I don't think it is recoverable, it didn't worked for me).
If you want to create only a ROM only with ROOT, do not check any box.
Now click in Backup and wait a few minutes. If it asks to pack the ROM, click Yes.
Now click in To create updates for modified recovery and select the files.md5 file inside backup folder.
The backup is complete. It is in the backup folder, and works with SP Flash Tool and CWM.
How to flash with stock ROM​
Be sure that you have CWM installed and the preloader drivers succefully installed!
Turn off your phone and start with CWM (Volume Up + Home + Power). Click in wipe data/factory reset and YES, the same for wipe cache partition and go to advanced. Now click in Wipe Dalvik Cache and do YES, the same for Wipe Battery State. Go back.
Open the SP_Flash_Tool_v3.1312.0.139 folder and open Flash_tool.exe.
Click on Scatter-loading button. Go to the 20130517_e2006_v89_jbla768_asx folder and select the MT6589_Android_scatter_emmc.txt file. Be sure that you have all the options selected like in the print.
​
Now this is a very quick step! In the main CWM menu in the phone, click in reboot system now.
Now go to the Smart Phone Flash Tool window. When the Windows makes the hardware inserted sound, you must click in the Firmware -> Upgrade option. If you hear the sound of hardware disconnected before the tool does it job, you must restart your phone and do this again.
If the Flash tool flashed the cellphone successfully, it will auto boot as the first time.
This means that you did the trick!
This thread will be updated to add more tutorials as requested or if I need to add something.
I will notify with a comment to the thread.​

Requests
IvanSantosPT said:
If you are interested in this phone, you can found it here:
http://www.geekbuying.com/item/Star-...ey-316069.html
This thread is ONLY for support of the Star S9500!
The Review topic is here:
http://forum.xda-developers.com/showthread.php?t=2458161
Support thread for Star S9500​
Topics:
Essential tools;
Installing drivers
How to ROOT;
How to remove China Apps;
How to change screen's DPI;
How to install CWM;
How to make a backup;
How to flash with stock ROM (tomorrow I will post);
Solving Messages app BUG (tomorrow I will post);
Solving any GPS issues (tomorrow I will post);
Changing the Launcher (tomorrow I will post);
Changing the Resolution up to 960p (tomorrow I will post).
Essential tools​
Here is a list with download links for some indispensable tools:
Notepad++
Drivers
MTKDroidTools
SP Flash Tool v3.1312.0.139
Installing Drivers
Preloader​
We will start with the Preloader driver, which is the trouble one.
First of all, shutdown the Phone.
Go to the Start Menu, right click in the Computer, and click Manage. Then go to the Device Manager.
Now you need to be quick! Connect the Phone to the computer via USB cable, and when appears MT65xx Preloader as unknown driver, right click in the device, Update Device, select the second option, select the folder mt65xx+preloader+drive that you downloaded and check the Include Subfolders option. Now let it install. Once installed, it will disappear, that's the reason that I said to be quick. The Preloader disconnects when the device is not in use and goes to charging mode.
Now you can turn on the device.
ADB Driver​
This is the easy one. Connect the phone in debugging mode, and in the Device Manager it will appear another driver to install.
This time you only need to select the MTK_USB_ Driver folder and it will install!
How to ROOT​
Download the MTKDroidTools which is in the Essential tools section, create a folder and extract the files.
If the drivers are installed and the device is in debugging mode, it will appear a green block at bottom left side like this:
Go to root, backup, recovery section, then click on SuperUser option. Click on YES to every option that will show up. You can select SuperSU app or the SuperUser app. I selected the SuperSU. Now click on Reboot at bottom right corner
Now you have your device rooted!
How to remove China Apps​
In the same section as in the ROOT tutorial, you this time click in Delete china.
How to change the screen's DPI
Preparing the scenary​
This gives a better look to the screen and it will look like Galaxy S4.
I changed the DPI because of the 240 DPI to 480x854 screen is so huge that hurts my eyes, and I have so small space to the apps!
We will prepare the work to you don't manually edit anymore the build.prop file, just this time.
So, lets begin. You need ROOT to do this!
Open the Root Explorer, go to the system folder, keep the finger at the build.prop file and select Copy.
Now go back to the root (/), go to the sdcard folder and select Paste.
Now connect the phone to the Computer and enable the USB file transfer.
Go to the phone internal memory by your Computer, and edit the build.prop file with Notepad++ to preserve the Unix Style of the text. Go to the end and add the following line:
Code:
ro.sf.lcd_density=240
Save the file. We have set the DPI to 240, but we will change it later in an easier way.
Now let's put the file back to the phone.
Go to Root Explorer and go to the /sdcard directory. Now press the build.prop file and click the Move option. Go back to root, go to the system folder, click in Mount R/W and click in Paste. Overwrite the file.
Changing the DPI​
Now we can do the trick with the MTKDroidTools.
Go to MtkDroidTools folder, and edit the build_prop_replace.txt file.
It must have this code inside:
Code:
ro.sf.lcd_density=240
You can change to a DPI between the 120 and 320 I think. Higher the DPI, higher the icons, less space for them.
You can calculate here the right DPI for your screen:
http://pxcalc.com/
Insert the data just like I did:
Seems like the right DPI to the screen is 195 DPI.
You can test this inserting the 1080x1920 resolution with 5 inch. If it gives us 440 DPI, that is the correct DPI from Galaxy S4 specs from GSMArena.
Now change the 240 value to 195:
Save the file and go to MTKDroidTools.
Go to the root, backup, recovery section and click in build.prop option.
Then click Reboot to reboot the device.
Compare here the difference between 240 DPI (left) and 195 DPI (right) screen:
​
Now when you want to change DPI you only need to do this steps.
How to install CWM​
To install CWM on the phone, open the MTKDroidTools and go to the root, backup, recovery section.
Click on To use boot from phone and click the Recovery and Boot button.
Now click Yes to every option.
Now you can access to CWM recovery by pressing Volume Up + Home + Power, and the Volume Down + Home + Power stock recovery is still working.
How to make a backup​
To backup you whole ROM, open the MTKDroidTools and go to the root, backup, recovery section.
If you want to backup your personal data to a personal backup, check the Backup userdata and cache box (I don't think it is recoverable, it didn't worked for me).
If you want to create only a ROM only with ROOT, do not check any box.
Now click in Backup and wait a few minutes. If it asks to pack the ROM, click Yes.
Now click in To create updates for modified recovery and select the files.md5 file inside backup folder.
The backup is complete. It is in the backup folder, and works with SP Flash Tool and CWM.
This thread will be updated to add more tutorials as requested or if I need to add something.
I will notify with a comment to the thread.​
Click to expand...
Click to collapse
Hi Ivan, I just wanted to thank you for the time you took to make this guide. You see, I'm from Argentina, and i bought this phone. It is excellent. The only problem I had, is that for example, I can use the phone all day without issues, but after a day or less, when i try to open an app, it just closes itself, and every app that i try to open does the same thing. The only thing that solves this is restarting the phone. Anyway, it isn't a big issue but it becomes a pain in the *** when you're trying to work. So after a few weeks, I reached the conclusion that it may be a problem with the stock ROM. In this post, you said that you were going to update the method to flash with the sotck rom, but you didn't. I wanted to know if you could help me with this, and to know if you had the same issue. Thanks for everything, and I'll be waiting for your answer

JaxDrive said:
Hi Ivan, I just wanted to thank you for the time you took to make this guide. You see, I'm from Argentina, and i bought this phone. It is excellent. The only problem I had, is that for example, I can use the phone all day without issues, but after a day or less, when i try to open an app, it just closes itself, and every app that i try to open does the same thing. The only thing that solves this is restarting the phone. Anyway, it isn't a big issue but it becomes a pain in the *** when you're trying to work. So after a few weeks, I reached the conclusion that it may be a problem with the stock ROM. In this post, you said that you were going to update the method to flash with the sotck rom, but you didn't. I wanted to know if you could help me with this, and to know if you had the same issue. Thanks for everything, and I'll be waiting for your answer
Click to expand...
Click to collapse
Hi JaxDrive, thank you for the opinion
I had some documentation to present in the school, so I didn't had time to do, but I will do in a few hours I think.
By the way, try to install this Launcher:
https://play.google.com/store/apps/details?id=com.gau.go.launcherex
The stock Launcher had some bugs, and I think that would be because of the stock Launcher, so I've installed this, which it gives better look also!

RE
Oh, sorry then for my bad aproaching to the topic haha :fingers-crossed:. Anyways, it's good to know that someone has the same phone as I do (only that I have the white version), and knows about programing, to help this noob to sort this issues out :B. Anyway, I already changed the launcher, because the stock one was buggy and ugly, but mostly ugly :laugh:. I'm currently using the Nova Launcher, which is pretty and works wonderfull. Like I said, the only problem that the phone has, is the apps closing themselves issue, which now became pretty annoying . I though that as you posted the method to have CWM recovery on our phone, if I'm able to get in my hands the original ROM of our phone, I can flash it, and hopefully fix this problem. But work at your own speed, I'm sure you have other things to care about besides this. So thats it, if you could provide the next tutorials about our phone, I would be very gratefull. Also I saw in one of your previous posts that you succesfully overclocked our processor, that would be an interesting feature too

JaxDrive said:
Oh, sorry then for my bad aproaching to the topic haha :fingers-crossed:. Anyways, it's good to know that...
Click to expand...
Click to collapse
How to flash with stock ROM​
Be sure that you have CWM installed and the preloader drivers succefully installed!
Turn off your phone and start with CWM (Volume Up + Home + Power). Click in wipe data/factory reset and YES, the same for wipe cache partition and go to advanced. Now click in Wipe Dalvik Cache and do YES, the same for Wipe Battery State. Go back.
Open the SP_Flash_Tool_v3.1312.0.139 folder and open Flash_tool.exe.
Click on Scatter-loading button. Go to the 20130517_e2006_v89_jbla768_asx folder and select the MT6589_Android_scatter_emmc.txt file. Be sure that you have all the options selected like in the print.
​
Now this is a very quick step! In the main CWM menu in the phone, click in reboot system now.
Now go to the Smart Phone Flash Tool window. When the Windows makes the hardware inserted sound, you must click in the Firmware -> Upgrade option. If you hear the sound of hardware disconnected before the tool does it job, you must restart your phone and do this again.
If the Flash tool flashed the cellphone successfully, it will auto boot as the first time.
This means that you did the trick!

Dude, you're awesome . Many thanks for the tutorial and sorry for the time that I made you lose. I just found the link that you made for the ROM haha. I'm flashing it in a couple of minutes. I'll post some feedback when its done c:

Isnt a lost time! I said that I will support the phone and I will do as long as I can
About the overclock, I just need to learn to compile the kernel and sure that I will post for everyone!
Sent from my 06_v89_jbla768_asx using xda app-developers app

Thanks a lot for your great work and for the time you spend on this post.
Stay tuned to follow the other steps you listed. :good:

Hello,
Dude i cannot manage to install the preloader drive!
I disconnect the phone, next i connect it via usb but nothing happens!
Does anyone can help me with that, i realy apreciated?

I managed to acess the preloader by by this method
1>TAKE THE BATTERY ,SD ,SIM OUT OF THE PHONE
2>HOLDING VOLUME+ CONNECT IT TO PC VIA USB(ONCE YOU HEAR A SOUND FROM PC YOU CAN RELEASE VOLUME+)
3>OPEN DEVICE MANAGER(ON COMPUTER SEARCH IT OR CONTROL PANEL)
But i get the error "Windows was unable to install...."
Windows 7 OS
Strange

Hello,
I'm having trouble to root the phone, see image bellow.
Also i bought this Star S9500 (S4 5" SmartPhone Mobile S9500 - Android 4.2 Dual SIM Quad Core MTK6589 12MP Cam)
on ebay but the cpu hardware is different from ebay, as seen on picture.
Any help on root will be apreciated and about the cpu hardware also

Try installing the drivers like I explained
Sent from my 06_v89_jbla768_asx using xda app-developers app

IvanSantosPT said:
Try installing the drivers like I explained
Sent from my 06_v89_jbla768_asx using xda app-developers app
Click to expand...
Click to collapse
The drivers are installed.

Hello,
Dude i cannot manage to install the preloader drive!
I disconnect the phone, next i connect it via usb but nothing happens!
Does anyone can help me with that, i realy apreciated?

Hello,
Yes, sorry, the drivers problem is already solved!
I Installed the pre loader drivers successfully, but i'm still unable to root the phone as you can see in the picture above.
Can anyone help me with this?
Thanks

Hello,
Can anyone give me some support please?

Tyto said:
Hello,
Can anyone give me some support please?
Click to expand...
Click to collapse
what support do you need?

Hello,
I'm having trouble to root the phone, see image bellow.
Also i bought this Star S9500 (S4 5" SmartPhone Mobile S9500 - Android 4.2 Dual SIM Quad Core MTK6589 12MP Cam)
on ebay but the cpu hardware is different from ebay, as seen on picture.
Any help on root will be apreciated and about the cpu hardware also
Click to expand...
Click to collapse
This, the full post is in the beginning of this page!

Any ideas how to root this?

Thanks!
Hey IvanSantosPT,
at first I want to thank you so much for for sharing your experiences and possibilities about that Phone! You cant find so much support for that phone at the hole web.
I bought my star s9500 at amazon and hope, that it will come quickly to my country. So, I allready started to download your content to be prepared for the arrival.
But I have one question: Is it really possible to set the screenresolution higher? ...up to 960p,like you write? or did I confound some details?
Greets from Germany!

CUBOT S200 root guide

CUBOT S200 root guide
Introduction
After a couple of months of searching for information, failing to get correct instructions from the seller and trying all available and often shady one-click root programs, I have finally successfully rooted my CUBOT S200 device.
In fact, all thanks go to rfax from this spanish forum:
http://www.movilesdualsim.com/tema/cubot-s200-root-y-recovery.93358/
The point of my post is to provide the same information in english and here, on the most widely read forum, xda-developers.com.
Before giving any instructions, I feel like I have to caution anyone trying this that I can accept no responsability for anything happening to your smartphone, as a result of following this guide. You are on your own and neither me nor anyone else is responsible for any damage, job loss, broken relationship, death or mass destruction
Also, make sure you BACKUP whatever you don't want to lose!
This rooting process should not result in any data loss, but it's always a good idea to BACKUP your stuff. So, if you have data on your phone for which you have no BACKUP, this is just a good opportunity to BACK IT UP.
Although it may seem obvious to some, please read the ENTIRE guide, BEFORE actually doing anything. This will allow you to have a general idea of the procedure and plan your steps.
Preparation
The hardware you are going to need is:
CUBOT S200 android smartphone (duh)
Windows PC
USB-microUSB data cable
My desktop machine is on linux, so in order to root my CUBOT S200, I used a Windows 7 netbook. I am pretty sure any Windows PC should do, but you definitely need a Windows machine for these instructions.
I have not even looked into the existence of an equivalent tool for linux or mac. If anyone has any information, please share and I would be glad to update the guide accordingly.
Here is a list of the software I used:
SP Flash Tools v5.1408.00
download here [RAR]
SuperSU
download here
You can find information about the latest version here
Recovery
download here
Drivers
download here
You should unzip/unrar all files, except for the SuperSU. Just keep the SuperSU zip file. It should be copied to the phone, either the internal memory or the external SD, if available. Just to be sure, I would recommend that you copy it to both locations. You can always delete it after you are done rooting the S200.
Inside the drivers zip file there is a folder and another folder inside it with a ...3rd folder in it and two executables, install & uninstall. The install is the one you will be using.
If you already have the required drivers installed, you can ignore these. If SP Flash Tool cannot proceed with the "download" as it calls it, then you need the drivers. More on that in the steps below.
Instructions
Overview
You will flash the Clockworkmod (CWM) recovery image to your phone using the SP Flash Tool.
You will then boot your phone into recovery and install the SuperSU program from the zip file.
That's it, just reboot and you have a rooted CUBOT S200!
Remember to BACKUP any data you have not already BACKED UP, or carelessly ignore this message, root your phone without any problems and then a few days or weeks later lose stuff for any unrelated reason and bang your head against a wall for not having seized this opportunity to BACKUP your sh*t.
Here goes:
Step 1
1. Make sure you have the SuperSU zip file. DO NOT UNZIP. If you downloaded from the link provided, the file should be named UPDATE-SuperSU-v2.46.zip
2. Copy this file to you S200. If you have a SD card, copy to both the SD card and the internal memory, so you can definitely find it in the recovery.
Step 2
1. Power off your phone
2. Remove the battery
Step 3
Make sure you have unzipped the Recovery. There should be a folder named "Recovery CWM" inside, including 2 files: MT6582_Android_scatter.txt and recovery.img
Step 4
1. Make sure you have downloaded and unrared the SP Flash Tool. You should have a folder named SP_Flash_Tool_v5.1408.00
2. Run the tool, it should be a file named flash_tool.exe
3. Click on the button Scatter-loading
4. Find the folder Recovery CWM from step 3 and choose the file MT6582_Android_scatter.txt. Make sure only RECOVERY is checked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Click Download. The Download button should be grayed out and Stop should be green or active anyway
Ok, let's make a new step for clarity.
Step 5
6. Put the battery in your phone. DO NOT TURN ON your phone
7. Connect your phone to the PC with the USB cable. DO NOT TURN ON your phone
8. A red full progress bar should appear at the bottom of the SP Flash Tool window, then a yellow bar should fill up (pretty quickly). When the yellow bar reaches 100%, a small window will pop up saying Download Ok!
9. Close the popup window. Close the SP Flash Tool. Disconnect your phone. You now have CWM recovery on your S200
Step 6
1. Press and hold down your phone's Volume Up button. DO NOT LET GO
2. Without letting go the vol+, press and hold down the Power button. Hold BOTH buttons down
3. The white CUBOT startup screen will appear and a few seconds later the phone will enter the CWM recovery mode. Now you can let go both buttons
(not the exact things you will see, just for illustration)
4. Using the Vol+/- buttons, choose Install zip from sdcard. Click the power button
5. Then Choose zip from sdcard
6. Find the SuperSU zip that you copied to your phone in step 1 and confirm with the power button
7. Choose Yes - Install
8. Once SuperSU is successfully installed, you will be back at the first screen. Choose Reboot system now
Step 7
Not really a step. Your phone should reboot (don't hold down any buttons) and you should now have root access!
Enjoy!
Unlimited thanks to rfax from the spanish site, where I found the instructions, http://www.movilesdualsim.com/tema/cubot-s200-root-y-recovery.93358/.
I am not an expert on these matters, but feel free to ask anything and I am sure someone, maybe even me, will step up and help you.
If you find any typos, mistakes, errors or have any remarks, which would make this guide better, please let me know and I will do my best to keep this post current and helpful.
Cheers,
panda2005
No kittens were harmed during the production of this guide.

Cant go into recovery Mode
panda2005 said:
CUBOT S200 root guide
Introduction
After a couple of months of searching for information, failing to get correct instructions from the seller and trying all available and often shady one-click root programs, I have finally successfully rooted my CUBOT S200 device.
In fact, all thanks go to rfax from this spanish forum:
http://www.movilesdualsim.com/tema/cubot-s200-root-y-recovery.93358/
The point of my post is to provide the same information in english and here, on the most wide read forum, xda-developers.com.
Before giving any instructions, I feel like I have to caution anyone trying this that I can accept no responsability for anything happening to your smartphone, as a result of following guide. You are on your own and neither me nor anyone else is responsible for any damage, job loss, broken relationship, death or mass destruction
Also, make sure you BACKUP whatever you don't want to lose!
This rooting process should not result in any data loss, but it's always a good idea to BACKUP your stuff. So, if you have data on your phone for which you have no BACKUP, this is just a good opportunity to BACK IT UP.
Although it may seem obvious to some, please read the ENTIRE guide, BEFORE actually doing anything. This will allow you to have a general idea of the procedure and plan your steps.
Preparation
The hardware you are going to need is:
CUBOT S200 android smartphone (duh)
Windows PC
USB-microUSB data cable
My desktop machine is on linux, so in order to root my CUBOT S200, I used a Windows 7 netbook. I am pretty sure any Windows PC should do, but you definitely need a Windows machine for these instructions.
I have not even looked into the existence of an equivalent tool for linux or mac. If anyone has any information, please share and I would be glad to update the guide accordingly.
Here is a list of the software I used:
SP Flash Tools v5.1408.00
download here [RAR]
SuperSU
download here
You can find information about the latest version here
Recovery
download here
Drivers
download here
You should unzip/unrar all files, except for the SuperSU. Just keep the SuperSU zip file. It should be copied to the phone, either the internal memory or the external SD, if available. Just to be sure, I would recommend that you copy it to both locations. You can always delete it after you are done rooting the S200.
Inside the drivers zip file there is a folder and another folder inside it with a ...3rd folder in it and two executables, install & uninstall. The install is the one you will be using.
If you already have the required drivers installed, you can ignore these. If SP Flash Tool cannot proceed with the "download" as it calls it, then you need the drivers. More on that in the steps below.
Instructions
Overview
You will flash the Clockworkmod (CWM) recovery image to your phone using the SP Flash Tool.
You will then boot your phone into recovery and install the SuperSU program from the zip file.
That's it, just reboot and you have a rooted CUBOT S200!
Remember to BACKUP any data you have not already BACKED UP, or carelessly ignore this message, root your phone without any problems and then a few days or weeks later lose stuff for any unrelated reason and bang your head against a wall for not having seized this opportunity to BACKUP your sh*t.
Here goes:
Step 1
1. Make sure you have the SuperSU zip file. DO NOT UNZIP. If you downloaded from the link provided, the file should be named UPDATE-SuperSU-v2.46.zip
2. Copy this file to you S200. If you have a SD card, copy to both the SD card and the internal memory, so you can definitely find it in the recovery.
Step 2
1. Power off your phone
2. Remove the battery
Step 3
Make sure you have unzipped the Recovery. There should be a folder named "Recovery CWM" inside, including 2 files: MT6582_Android_scatter.txt and recovery.img
Step 4
1. Make sure you have downloaded and unrared the SP Flash Tool. You should have a folder named SP_Flash_Tool_v5.1408.00
2. Run the tool, it should be a file named flash_tool.exe
3. Click on the button Scatter-loading
4. Find the folder Recovery CWM from step 3 and choose the file MT6582_Android_scatter.txt. Make sure only RECOVERY is checked.
5. Click Download. The Download button should be grayed out and Stop should be green or active anyway
Ok, let's make a new step for clarity.
Step 5
6. Put the battery in your phone. DO NOT TURN ON your phone
7. Connect your phone to the PC with the USB cable. DO NOT TURN ON your phone
8. A red full progress bar should appear at the bottom of the SP Flash Tool window, then a yellow bar should fill up (pretty quickly). When the yellow bar reaches 100%, a small window will pop up saying Download Ok!
9. Close the popup window. Close the SP Flash Tool. Disconnect your phone. You now have CWM recovery on your S200
Step 6
1. Press and hold down your phone's Volume Up button. DO NOT LET GO
2. Without letting go the vol+, press and hold down the Power button. Hold BOTH buttons down
3. The white CUBOT startup screen will appear and a few seconds later the phone will enter the CWM recovery mode. Now you can let go both buttons
(not the exact things you will see, just for illustration)
4. Using the Vol+/- buttons, choose Install zip from sdcard. Click the power button
5. Then Choose zip from sdcard
6. Find the SuperSU zip that you copied to your phone in step 1 and confirm with the power button
7. Choose Yes - Install
8. Once SuperSU is successfully installed, you will be back at the first screen. Choose Reboot system now
Step 7
Not really a step. Your phone should reboot (don't hold down any buttons) and you should now have root access!
Enjoy!
Unlimited thanks to rfax from the spanish site, where I found the instructions, http://www.movilesdualsim.com/tema/cubot-s200-root-y-recovery.93358/.
I am not an expert on these matters, but feel free to ask anything and I am sure someone, maybe even me, will step up and help you.
If you find any typos, mistakes, errors or have any remarks, which would make this guide better, please let me know and I will do my best to keep this post current and helpful.
Cheers,
panda2005
No kittens were harmed during the production of this guide.
Click to expand...
Click to collapse
Hi I did all the steps and when i try to access recovery menu (Vol+ plus power button) it wont allow me to do so. It goes into a loop and just flashing the Cubot logo,
Please help me.

sopedyoi said:
Hi I did all the steps and when i try to access recovery menu (Vol+ plus power button) it wont allow me to do so. It goes into a loop and just flashing the Cubot logo,
Please help me.
Click to expand...
Click to collapse
In the Recovery zip you downloaded (see link in guide), there is also a folder Recovery Original.
In there you can find another scatter file, also named MT6582_Android_scatter.txt.
Flash this one and you should get the original recovery back.
Please, make sure you follow all the steps very carefully. Again, I know that people have followed this guide with success in the spanish site and I have done so too.
Hope that helps!

Thank you for sharing.

Working now!
panda2005 said:
In the Recovery zip you downloaded (see link in guide), there is also a folder Recovery Original.
In there you can find another scatter file, also named MT6582_Android_scatter.txt.
Flash this one and you should get the original recovery back.
Please, make sure you follow all the steps very carefully. Again, I know that people have followed this guide with success in the spanish site and I have done so too.
Hope that helps!
Click to expand...
Click to collapse
Thank you for the help!
Looks like is rooted now.
Now i have another question. i saw a post about converting 2G phones to 3G phones via fastboot. refer to link: http://forum.xda-developers.com/one...11s-modem-problem-t2824139/page5#post54753177
I will like to know if this is possible with this phone since i need the 1900 3G band on this phone.
Please let me know.

sopedyoi said:
Thank you for the help!
Looks like is rooted now.
Now i have another question. i saw a post about converting 2G phones to 3G phones via fastboot. refer to link: http://forum.xda-developers.com/one...11s-modem-problem-t2824139/page5#post54753177
I will like to know if this is possible with this phone since i need the 1900 3G band on this phone.
Please let me know.
Click to expand...
Click to collapse
I don't really know anything about that. Hopefully, someone will see this and come up with a solution, if it is indeed possible.
Congrats on rooting your phone, enjoy!

"A red full progress bar should appear at the bottom of the SP Flash Tool window, then a yellow bar should fill up (pretty quickly). When the yellow bar reaches 100%, a small window will pop up saying Download Ok!"
No bar appears for me....

mchart03 said:
"A red full progress bar should appear at the bottom of the SP Flash Tool window, then a yellow bar should fill up (pretty quickly). When the yellow bar reaches 100%, a small window will pop up saying Download Ok!"
No bar appears for me....
Click to expand...
Click to collapse
Maybe the drivers are not successfully installed. Try rebooting your computer and/or installing the drivers again.

Windows 10 drivers
First of all, thanks gor the great guide! I am now rooted.:good:
I did run into a problem with the drivers though. They don't work with Windows10. After looking around a bit I found a great guide with drivers that did work.
Here's the link.
(Sorry but I can't post outside links. You'll have to copy and paste to your browser.)
laurentiumihet.ro/technology/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
Enjoy!

Trouble with red full progress bar
Hi
I put the battery in my phone. My phone is off
I connect my phone to the PC with the USB cable.
But nothing red full progress bar appear at the bottom of the SP Flash Tool window
Can you explain to me why this happens?
Thank's
Ardi

Custom ROM for Cubot S200
Hi Panda2005.
Thanks for excellent post on rooting the S200.
I have tried several rooting tools and they all failed for one reason or another and your method worked first time.
I am new to Android and find it a little confusing compared with Windows but I am learning!
My question is can you recommend a custom ROM suitable for the S200?
Thanks again.

nailbender7 said:
Hi Panda2005.
Thanks for excellent post on rooting the S200.
I have tried several rooting tools and they all failed for one reason or another and your method worked first time.
I am new to Android and find it a little confusing compared with Windows but I am learning!
My question is can you recommend a custom ROM suitable for the S200?
Thanks again.
Click to expand...
Click to collapse
I am glad you managed to root your phone.
Actually, I have never tried any custom ROMs, so unfortunately I could not recommend any.
I have since bought a new phone, so I have not played with the S200 in over a year. A friend of mine has borrowed it, but he has not looked for custom ROMs either.
If you find/try any cool ones, feel free to let me know here.
Good luck!

Re Cubot s200
Hi Panda 2005,
Yes I too have come to the conclusion that the S200 does not have a big enough following in order to warrant much interest from the techies capable of creating such ROMs.
As a matter of interest can you recommend a phone with plenty of ROMs available for experimentation?
I have been looking at a second hand Samsung S4. Not too expensive if I brick it!

Sorry, I have not dabbled with custom ROMs in a few years, not since I had a ZTE Skate Acqua. Good times!