Database Info

[GUIDE] Beginner's guide - first steps with a MTK phone

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
This guide may be obsolete now for the new MTK SOC's powered phones, but it will give you some ideeas about how MTK phones world works (especially if you are new to this).
Why this thread?
- Because of all those PMs I receive with questions about how to do this or how to do that.
These things aren't they covered here on XDA?
- Some of them are, some don't, or they are spread over the forum in different sections, different threads. Also I will present here my vision about how to do things, and in some parts is different than the others existent.
I tried to document all steps with images for a better understanding, and to make it easy for people who don't understand well English (also I don't claim that my English is very good, but I'm trying).
1. If you want to use your phone as you buy it, then this thread is not for you, but if you want to use a custom recovery, to install a custom ROM, or some modds, keep reading.
2. First big step in our journey is to root your phone, which most of you know that means to get root (administrator) access to your phone's OS - just a simple definition. With an unrooted phone, you can't do much, and that means you will use it pretty much as you buy it - see first point.
There are multiple methods to root your phone, through an application from your phone, with an executable software from your PC or by flashing a zip modd from recovery (only for custom recoveries).
A. The best rooting application at the moment (in my opinion), is Framaroot.apk, developed by alephzain - please stop by his thread and drop a thanks, or if you can buy his donnation app from Playstore to support his work. You can download this app from official thread.
B. For rooting with a software from PC, I know three big candidates: oneclickroot, kingoroot and srsroot. I know there are more, but I mentioned only the best known.
C. Rooting zip archives are two, to choose from: chainfire's and koush's. Although, these require to have a custom recovery installed.
Any method you choose, be sure to check the phone models reported to work for, and look for your model.
Next, I will present step by step what I call "the beginner's routine":
root the phone;
make a nvram backup;
make a stock ROM backup;
generate a custom CWM and flash it;
patch to unsecure the boot and flash it;
get a Root File explorer;
create a custom recovery by porting one.
Prerequisites:
you must have an account on XDA; if you don't, then create one - and remember, at beginning you will not be allowed to post but you can hit Thanks for people I will mention here.
use a computer with Windows XP or 7 (I don't know if it will be any problem in vista or windows 8, but I didn't tried them, so I can't tell).
a phone with MTK CPU, obviously!
these tools:
MTKDroidTools of rua1's - download it from his thread and hit Thanks or donate to him, please
SPFlashTools or MTKFlashTools.
MTK USB Drivers and your phone manufacturer's USB Drivers if they provide that.
For MTK USB Drivers, there are many sources, but I couldn't find any official source. Few known sources: here and here.
* ADDED: For windows 7 and xp I repacked all MTK needed drivers, bundled with latest google usb drivers and using windows driver installer. Some of the drivers are not digitally signed, so when the prompt window ask you if you want to install unsigned driver (it will be several times) select yes or ok. The advantage is that this method is easier than manual method and also will create an entry in installed programs, and later if you want you can uninstall them in control panel uninstall program. Before installing this you need to remove old drivers installations - use usbdeview (download it x86 or X64), and look for VendorId 0bb4 and 0e8d, and uninstall every device with these Ids. Packed drivers are attached to this post; take what corresponds to your windows version. Unpack the archive, open the folder and run dpinst.exe. More info inside: read info.txt (especially for XP).
Install all needed drivers.
A good text editor (Notepad++ or Geany) installed.
Adb installed in your computer from Android: here, here and here you can learn how.
Credits and Thanks:
@alephzain - Framaroot developer
@rua1 - developer of MTKDroidTools
@Chainfire - SuperSU developer
@Koush - so many things!!!
@michfood - developer of Boot Recovery pack/unpack tool
and, even if it is not presented here, but because I use a lot his tools in Linux:
@bgcngm - for his Unpack/Repack scripts

1. Root the phone.
For this step I choose to use Framaroot.apk, first because I don't like to install unnecessary software on my computer, and second because it supports a very large number of MTK phones. So, go to alephzain's thread and download the apk, then connect your phone to PC with USB debugging enabled, turn on USB Mass storage and copy Framaroot.apk to your sdcard root, or in internal storage if you don't have a sdcard in your phone. Eject phone's USB storages from PC, and turn off USB Mass storage from phone.
{
"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 apps drawer, find File Manager, open it, navigate to location where you placed Framaroot.apk touch on it and install it. After that go back in apps drawer and open the newly appeared Framaroot. In that window you have to specify which exploit to use for getting root access. If you don't know it's not a problem, you can try each one until you see the Success message (for me was Barahir). If none of them works, then you have to find a different method to root. After success patching, reboot the phone and then you will see SuperSU.apk in your apps drawer. Now you have root access!
2. Install a Root Explorer.
I prefer ESFileManager, but you can choose what you like. This can be installed free from Playstore, or if you have it downloaded in your PC, use same steps as in Framaroot case, and install it.
Then open the app and let's activate the Root Explorer in it.
But, here you can choose a different view style instead of default big icons - I like Medium Icon view.
Touch on Globe symbol from upper left corner to open Advanced Tools menu, and select Tools (last one). In the list that opens, scroll down until you see Root Explorer entry and touch "OFF" button to activate it. You will be prompted to Grant Superuser access - Grant it! Then, touch on "Root Explorer" text and in the popup window select Read/Write, and in next window select all radios from RW column.
That's it, ESFileManager is now a powerfull Root Explorer.

3. Make a backup.
This means actually make two backups, one for nvram and one for the whole stock ROM. Why to make a backup for nvram? Because it is very easy in MTK phones to mess up with it, and you may loose IMEI, mac address or to have other connectivity issues. This backup will be your insurance.
For this you need MTKDroidTools. Download it from rua1's thread (link in OP) and unzip it in a folder named "MTKDroidTools" on your primary (system) partition - this is important, and in other locations you may experience errors and malfunction.
Connect your phone in usb debugging mode to PC, then start MTKDroidTools as administrator and wait untill you see that MTKDroidTools recognize it and loads its data. The following pictures will show you how to check if you have usb debugging activated, and how MTKDroidTools looks with loaded phone data. In most of the phones, adb gets root access immediately, but in some "branded" ones that has to be achieved by click on the "ROOT" button next to "Adb Terminal" - Notice that if you don't see that ROOT button, that means you have already "root in shell". Also, if you have chainfire's SuperSU you will be prompted in the phone to grant root access to adbd, but if you have koush's Superuser, adbd gets root access by default.
Now, as I said first thing is to do a nvram backup. Click on "IMEI/NVRAM" button and next select both methods (bin and zip folder) and click on "Backup".
After that, it's time to do a stock ROM backup. This is important if you are going to try different custom ROMs and modds. This will assure you that you always have a way to start from the beginning in a clean state. Also makes easy to unbrick your phone if you have the misfortune to brick it.
Click on "root,backup,recovery" tab, and click on "Backup" button, then wait to finish. Be patient, this will take a while, and you can see progress logs in side window. At the end, a popup will prompt you to pack the backup. Now you know it is finished. I don't pack these backups, but you do what you think.
In this stage first thing I do is to generate a scatter file. You have one in that backup made before, or you can get one from stock firmware archive if the phone's manufacturer provide that, but let's see how to do it as it is, to understand the process, or to learn how to get one if we loose it or we are unsure if the one we have is good for our phone (this is important, because using a wrong scatter file it may damage your phone).
So, return to "Phone Informations" tab and click on "Blocks Map" button. A window opens with your phone partition structure. Click on "Create Scatter File" button and save it somewhere in your computer.
Mission complete for backup; you are assured now.

4. Generate a custom recovery.
This is mandatory if you want to use an easy way to backup, restore, flash or wipe ROMs and modds. Fortunately, rua1 has included in his tool all you need to generate one for your phone. This method is successfull for almost every MTK phone, but not for all. There isn't an universal method for anything.
So, enter again in "root, backup, recovery", select the radio "To choose the boot.img file" - by default is selected "Install already prepared files" - and click on "Recovery and Boot" button.
When prompted, select the boot.img from previous backup folder and click Yes to make CWM recovery automatically. First you will be prompted to flash a patched boot.img in your phone - click Yes to get an unsecured boot, then next message will ask you to install the new created recovery in your phone. Click Yes and Yes to reload the phone in recovery mode.
The phone will shut down and reboot in recovery. Now you can see your custom recovery in place.
GOOD TO KNOW: you can't generate a recovery everytime you want to flash one, to use MTKDroidTools for flashing, and the adb method may not work for many MTK phones.
The most known method to flash a new recovery is by using SPFlashTools or MTKFlashTools, and an alternative method is with MobileUncle application from phone, but I will show detailed the FlashTools method. One thing though: if you want to use MobileUncle application, you have to use it from /system/app folder, not from /data/app. Many users say that the MobileUncle doesn't work to flash recovery: it show success, but rebooting to recovery reveal the old one. The reason? They installed MobileUncle from market, and that place the app in /data/app as a user app. In custom ROMs where the app is placed in system by ROM developer, the problem won't manifest. So, if you want to use MobileUncle, make it a system app not user app.
In order to do that, grab a copy of any of these tools from DR_MOOSAVI's thread (link in OP), unzip it in a folder "MTK_Flash_tool" in your primary(system) partition (C in my case), and notice the name have to not contain any spaces or special characters. In that folder create a new folder "Resources" or ROM or whatever name you want, also without spaces or special characters, and place in it your scatter file and recovery img you want to flash. Open Flash_Tool executable as administrator.
IMPORTANT: Your phone is not connected to the PC now. Swtich it off and wait, you will connect it later.
Continue in next post.

In Flash_Tools program window click on load scatter file, navigate to that folder you created and select your scatter. Now you can see your phone's partition structure. If the recovery you want to flash is named "recovery.img" it will be selected automatically, if not you have to click on recovery row in Location column and select your recovery from that folder.
Then click on "Download" button.
Now connect your phone to PC, just like that in power off. Some models enter automatically in download mode and the flashing process begins, but others don't. For some it is necessary to connect them without battery (battery removed), other need to press briefly Power and Vol Down button at same time and release them immediately. That you have to find for your phone from forums, other users, or by trying. When the phone enter in download mode you will see a red bar down in Flash_Tool window, followed by a yellow or other color one (that means the flashing process is taking place).
At the end a popup with a green circle or green checkmark will let you know that the flash was a success. Deconnect the cable and reboot the phone, or reboot it in recovery to see if the wanted recovery is installed. The most common method to boot in recovery from power off is to press Power and Vol UP at same time, and keep them pressed untill you see the logo, then release Power but keep pressing Vol Up untill the recovery UI appears. If Power and Vol Up doesn't work for you, start the phone normaly and connect the phone to PC, then open a command prompt window, and type " adb reboot recovery", then hit Enter during bootanimation. The phone will stop loading and will boot in recovery.

5. How to port a custom recovery.
Check my new guide.

Check my new guide.

Awesome Tutorial!!! U did it again....
Thanks!!!

Thank you sir I will try to port cwm to my mtk mobile
Sent From MTK-MT6572
---------- Post added at 03:31 PM ---------- Previous post was at 03:01 PM ----------
Sir now my mobile with ext4
Now in your thread about porting carliv cwm.. there is only custpack and ubifs ...!! Where is for ext4
Sent From MTK-MT6572

carliv grt work hope u add this post too http://forum.xda-developers.com/showthread.php?p=49081376

[email protected] said:
carliv grt work hope u add this post too http://forum.xda-developers.com/showthread.php?p=49081376
Click to expand...
Click to collapse
Thanks, but that is not something for begginers. Maybe meteos method with his app will be, but I'm not sure. Though, if someone want to procede to do that, you can edit your post and give more details, for people to know what is about, and to follow your link if they are interested.

Great guide @carliv.
Just a bit confused, as I usually flash custom recovery first before rooting my MTK phones (same goes for all my android devices). So, maybe, rooting and flashing custom recovery is interchangeable as the first step for MTK phones depending on their availability.

iZLeeP said:
Great guide @carliv.
Just a bit confused, as I usually flash custom recovery first before rooting my MTK phones (same goes for all my android devices). So, maybe, rooting and flashing custom recovery is interchangeable as the first step for MTK phones depending on their availability.
Click to expand...
Click to collapse
Yeah, well the next step in my guide is "do a stock ROM backup", and if you flash a custom recovery, that will not be a complete stock backup. With my method, any time, after flashing the stock backup, unroot and you will be in stock initial state.
I hope it's more clear now.

carliv said:
Yeah, well the next step in my guide is "do a stock ROM backup", and if you flash a custom recovery, that will not be a complete stock backup. With my method, any time, after flashing the stock backup, unroot and you will be in stock initial state.
I hope it's more clear now.
Click to expand...
Click to collapse
Got it. So this is more suited for those who do not have the original firmware for restoring their devices in case something goes wrong which is so like MTK phones. In any case, your guide is spot on. Hope the moderators would give this a sticky, if possible, since MTK phones are scattered all over xda.

How to Port to Device that have recovery-from-boot.p
Hello Everyone, and hello to @carliv,
Thanks to this Tutorial I have Manage to port in on a MT6582 and MT6572 Device with ext4 partition, but I just want to share some tips when porting the latest build of the carliv the tutorial here is complete except for one thing just in case you are ending up on a custom recovery not booting up and when you use the MTK Droid Root and Tools you will see this
-->Connect Device<--
there is a file blah blah - recovery-from-boot.p <----
Now that mess up the things but before we dig into that let me first share on how I got my Carliv Custom Recovery to Bootup
on the Tutorial there is a section that you need to use the MTK Unpacked tool right now once you have done that do all the other things that is written in the tutorial it will guide you on the whole process but on my end even though I followed the tutorial and all are correct I still end up on a Bootloop well I discovered that you need to copy the init file from the RUA1 CWMR that you got from the MTK Droid Root and Tools and overwrite the one on the Carliv Recovery after that once you have finish until on the Overwriting of the Kernel and Kernel header pack your Carliv Recovery using the MTK pack tool and now Flash it on your Device it will now boot :highfive:
BUT WAIT!! yes! it will boot but it will boot on the STOCK RECOVERY and that is because like what I said the recovery-from-boot.p is the culprit of the issue now you need to root your device which is on my end I used framaroot and then download the ES file manager and also follow the instruction of carliv on how to have the full ROOT R/W access and on your device, once your have done that got to this folders and delete this 3 files.
Be sure you have the R/W access or else this files will not be deleted
/system/recovery-from-boot.p
/system/etc/recovery-install.sh
/system/etc/recovery-resources.bin <--- I am not just sure if this is the right filename but it is almost the same will check it once again once I got to stock rom again :fingers-crossed:
and now once you have rebooted your smartphone to recovery mode it will now boot to the Carliv Custom Recovery.
But also take note that if you don't have that 3 files on your device your just good to go and it will boot to Carliv Custom Recovery without any issues.
it's just that 3 files makes the custom recovery always boot to stock recovery even though you do something else
hope this tip helps for some people having issue on a bootloop carliv custom recovery on doing the manual porting
and don't forget to hit the thanks button if this helps :victory:

rnovino said:
/system/recovery-from-boot.p
/system/etc/recovery-install.sh
/system/etc/recovery-resources.bin <--- I am not just sure if this is the right filename but it is almost the same will check it once again once I got to stock rom again :fingers-crossed:
Click to expand...
Click to collapse
Removing recovery-from-boot.p is enough, I think. Besides, CTR asks if you want to disable recovery-install.sh. That prevents the ROM from flashing stock recovery.

iZLeeP said:
Removing recovery-from-boot.p is enough, I think. Besides, CTR asks if you want to disable recovery-install.sh. That prevents the ROM from flashing stock recovery.
Click to expand...
Click to collapse
it depends on the unit, I just deleted the recovery-from-boot.p and still it boots up on the stock recovery that's why I needed to trace other files that still makes it boot on stock recovery, but then again not all units will have the same issues as mine

Thanks for your help, it works with my Huawei Honor 3X (mtk6592) !

Thanks Man!

Error
Please help me in porting recovery.I am getting error "the syntax of the command is incorrect " in all four files.
View attachment 2654172
View attachment 2654177

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!

[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"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"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

[Guide] How to Root Cube T8 Plus

Hi
I found a russian site how to root the Cube T8 Plus h**p://4pda.ru/forum/lofiversion/index.php?t695306.html. Here a short translation:
Disclaimer: ******* I'm not responsible for any damages *******
1. Download SuperSu directly to your Cube T8 from official site: h**p://download.chainfire.eu/supersu
2. Download Flash Utility/Driver on your PC: h**p://uploaded.net/file/eyo5yt8c
3. Download TWRP for Cube T8 on your PC: h**p://uploaded.net/file/o54jinin and extract its content to a folder.
Mirror: https://drive.google.com/drive/fold...ourcekey=0-11J8nUVn2_sUUAPHA9kwWg&usp=sharing
4. Install Device Driver from Step 2. on your PC (you have to agree Security warning). Depending on Windows version used, disabling Driver Signing might be required prior installation.
5. Start flash_tool.exe
6. Go to "Download" tab and Click "Scatter-Loading" Button, move to folder created in Step 3. and select the file "MT6753_Android_scatter.txt". Press the "Download" Button
7. Power down your Cube T8 tablet. After power down, connect it to a USB Port on your PC (No, you don't need to power it up - leave it powered down!). After a few moments, the flash tool should recognise the tablet and will install twrp recovery and should show "Success" Screen
8. Remove tablet from PC. Boot into Boot Selection by pressing Volume-Up and Power button simultaneously, Select "Recovery" and wait for twrp booting up.
9. In twrp, Install Zip File downloaded on Step 1. This should be found in Folder "MyFavorite"
10. Reboot device. By selecting "Reboot" in twrp, the device will hang. But don't worry; just press the power button for about 10 seconds for a forced reboot.
11. Voilà, you have a rooted Cube T8 Plus

Thanks for the guide. Can you provide more mirror? Uploaded is currently blocked in my country. Google Drive would be sweet.
Thanks.

Anybody tried this?

It works perfectly, but I had to disable the driver's signature check.
Now I just need the modified scatter file to get a better memory repartition. These russian guys on pda.ru found out how to repartition the memory, but the file is now disappeared from internet http://4pda.ru/forum/index.php?showtopic=695306&st=560#entry44767726

Yes !
it worked for me but i didnt succeed in installing the right driver (package given in this post was correctly installed) for tablet in off mode,
so i had to force download of recovery and if SuperSU install (with error) when i launch it it warn for binary installation.
but root is effective and i can now use soft like adaway or else that need complete root access :victory:

LtGarcia said:
it worked for me but i didnt succeed in installing the right driver (package given in this post was correctly installed) for tablet in off mode,
so i had to force download of recovery and if SuperSU install (with error) when i launch it it warn for binary installation.
but root is effective and i can now use soft like adaway or else that need complete root access :victory:
Click to expand...
Click to collapse
That's weird, it worked flawlessly for me.
By the way, the internal 2 GB storage is way to small for me, I need a bigger partition and since the 4pda guys deleted their scatter files, I'm trying to create it by myself following this guide, I hope to not mess up things
Ok, I found the scatter editor (that was deleted too). Here you can download it. OP, if you want, you can add it in the guide.

Thanks for your feedback and your work Dyonysus, i assume all errors was consecutive to Kingroot installation (he didn't succeed in rooting but i left it installed when i flashed the recovery as i checked sometmes if a root policy was avaible)

This root guide can be used for Cube T8 also?

I also confirm this method works perfectly. Good job finding this.

Dionysus2389 said:
By the way, the internal 2 GB storage is way to small for me, I need a bigger partition and since the 4pda guys deleted their scatter files, I'm trying to create it by myself following this guide, I hope to not mess up things
Ok, I found the scatter editor (that was deleted too). Here you can download it. OP, if you want, you can add it in the guide.
Click to expand...
Click to collapse
So, have you succeeded in repartitioning the internal memory? If yes, did you face any issues or errors in the process and is the device stable and working as fast afterwards?

vorlonresident said:
So, have you succeeded in repartitioning the internal memory? If yes, did you face any issues or errors in the process and is the device stable and working as fast afterwards?
Click to expand...
Click to collapse
Unfortunately I didn't. I got a bunch of problems tryin' to forge the new scatter file and, when I finally got a decent one, the damn tool didn't flash it properly.
If someone could find those two files or just ask those russian guys to upload them again, it'd be terrific.

Hi,
This post is a subject to change (grow), since I will keep it as a record for my tips for this fine tablet.
Installation of TWRP recovery and increasing /data partition (YES! That's possible)
I've succeeded getting TWRP, root and larger /data partition, so after screenshot I'll put detailed how-to. Sorry for duplicating first post, but I'd like to have everything in one place in the way I exactly did it.
Warning: this method seems to be blocked in some newer OS updates, see this post for reference: http://forum.xda-developers.com/showpost.php?p=64801688&postcount=25
All credits go to OP and @odigitech for http://forum.xda-developers.com/general/rooting-roms/guide-how-to-resize-data-internal-t3180978
Screenshot:
{
"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"
}
You need SD card for that.
Cube T8 Plus TWRP and root:
1. Download SuperSu and copy it to the root of SD card (without extracting): http://download.chainfire.eu/supersu
2. Downlad Utility/Driver to PC: http://uploaded.net/file/eyo5yt8c
3. Download Cube T8 TWRP recovery to PC: http://uploaded.net/file/o54jinin and unpack.
4. Install driver on PC. Depending on Windows version, if the driver installation fails, it may be necessary to disable signature check (google for that).
5. Run flash_tool (downloaded in step 2). If it doesn't run, try copy it to the root folder of your hard drive, eg. C:\SP_Flash_Tool_exe_Windows_v5.1516.00\, albo D:\SP_Flash_Tool_exe_Windows_v5.1516.00\
6. In "Download" section choose "Scatter-Loading" point to "MT6753_Android_scatter" from /Recovery (downloaded in step 3), press "Download" button.
7. Turn off the tablet. Connect it via USB to PC (tablet needs to be switched off!). After short while, flashing tool should recognize the tablet and start flashing automatically, installing TWRP recovery. After that you should get "Success" screen.
8. Disconnect tablet from PC. Run it in Recovery by pressing VOLUME_UP and POWER simultanously.
9. Using VOLUME_UP, choose "Recovery" and confirm it by pressing "VOLUME_DOWN". Wait untill TWRP starts.
10. In TWRP choose 'install ZIP' and point to "/external sd/UPDATE-SuperSU-v2.46.zip"
11. After installation is finished, choose "Reboot". Recovery will hang, but do not fear Press Power for 10s to force turn off. Then turn on the tablet.
Your tablet is now rooted!
Change partition size:
1. Download and copy to the root of SD (without extracting) Resize_v22.4.1-signed.zip: (take attachment from the first post here: http://forum.xda-developers.com/general/rooting-roms/guide-how-to-resize-data-internal-t3180978/ )
2. Run the tablet in Recovery by pressing VOLUME_UP and POWER simultanously.
3. Using VOLUME_UP, choose "Recovery" and confirm it by pressing "VOLUME_DOWN". Wait untill TWRP starts.
4. In TWRP choose 'install ZIP' and point to "external sd/Resize_v22.4.1-signed.zip""
5. In one of following windows choose the partition size. I recommend between 8GB and 10GB. WARNING: If you choose less than the current size, you may loose your data. More than or equal to 8GB is a safe value.
Enabling Multiuser accounts:
1. The device must be rooted
2. Use any root explorer to edit /system/build.prop.
3. Add to the end of a file:
Code:
fw.show_multiuserui=1
fw.max_users=5
4. Reboot
Info: After first try to swich to guest the device force rebooted, but then it worked well.
Disabling killing background apps
If you encounter situation in which apps are being killed right after they are put to background (each application switch using recent apps causes application reinitialization), just make sure that Developer Options/Apps/Don't keep activities is switched off!
Permamently disabling pre-installed chinese apps (they will not reappear after full reboot)
There are 6 chinese apps pre-installed, which can be easily disabled. You can try to simply uninstall them, but you'll find that after full reboot they reappear.
So the best way to disable them is to use any root explorer and get rid APKs in /system/vendor/operator/app. I myself renamed app folder to app.old. They do not appear anymore.
What to do if tablet seems to be dead (black screen - no reaction), but it just misbehaves
Couple of times I've had a situation in which the screen was blank and I couldn't wake up the device. I could however run recovery, so the first time I performed reset from recovery and it helped.
Next time I found out that it's automatic brightness that fails and causes the screen to go blank. So the solution is to press power button, make a swipe gesture from the top to show brightness slider (you will not see it, but it works even on the lockscreen), and try to blindly press this slider. It should be about 2,7 cm (1,06 inch) from the top, with ca. 3cm (1,2 inch) margins on the left and right. Then stop using autobrightness with slider set to zero.

Thanks a ton
Amazing , followed your instructions and my tablet is now rooted and also has 9+GB of data partition. Thanks a ton.. Keep up the good work.
--Rao:

after using the resize script it not remount the partition and android not start. Android ask for a password to "decrypt data" but the problem is that the partition is missing.
Any suggest about this?
thanks
For the moment i can resize partition up to 6 gb using a edited scatter file

Please can I use this safely on the original Cube T8?

Zunera M said:
This root guide can be used for Cube T8 also?
Click to expand...
Click to collapse
The steps are the same! Only the files for drivers and TWRP Recovery change. I need to put a guide together for the T8.
Here's the link: http://forum.xda-developers.com/android/general/guide-how-to-root-original-cube-t8-t3285009

maludroid said:
Hi,
I've succeeded today getting TWRP, root and larger /data partition, so after screenshot I'll put detailed how-to. Sorry for duplicating first post, but I'd like to have everything in one place in the way I exactly did it.
All credits go to OP and @odigitech for http://forum.xda-developers.com/general/rooting-roms/guide-how-to-resize-data-internal-t3180978
Screenshot:
You need SD card for that.
Cube T8 Plus TWRP and root:
1. Download SuperSu and copy it to the root of SD card (without extracting): http://download.chainfire.eu/supersu
2. Downlad Utility/Driver to PC: http://uploaded.net/file/eyo5yt8c
3. Download Cube T8 TWRP recovery to PC: http://uploaded.net/file/o54jinin and unpack.
4. Install driver on PC. Depending on Windows version, if the driver installation fails, it may be necessary to disable signature check (google for that).
5. Run flash_tool (downloaded in step 2). If it doesn't run, try copy it to the root folder of your hard drive, eg. C:\SP_Flash_Tool_exe_Windows_v5.1516.00\, albo D:\SP_Flash_Tool_exe_Windows_v5.1516.00\
6. In "Download" section choose "Scatter-Loading" point to "MT6753_Android_scatter" from /Recovery (downloaded in step 3), press "Download" button.
7. Turn off the tablet. Connect it via USB to PC (tablet needs to be switched off!). After short while, flashing tool should recognize the tablet and start flashing automatically, installing TWRP recovery. After that you should get "Success" screen.
8. Disconnect tablet from PC. Run it in Recovery by pressing VOLUME_UP and POWER simultanously.
9. Using VOLUME_UP, choose "Recovery" and confirm it by pressing "VOLUME_DOWN". Wait untill TWRP starts.
10. In TWRP choose 'install ZIP' and point to "/external sd/UPDATE-SuperSU-v2.46.zip"
11. After installation is finished, choose "Reboot". Recovery will hang, but do not fear Press Power for 10s to force turn off. Then turn on the tablet.
Your tablet is now rooted!
Change partition size:
1. Download and copy to the root of SD (without extracting) Resize_v22.4.1-signed.zip:
2. Run the tablet in Recovery by pressing VOLUME_UP and POWER simultanously.
3. Using VOLUME_UP, choose "Recovery" and confirm it by pressing "VOLUME_DOWN". Wait untill TWRP starts.
4. In TWRP choose 'install ZIP' and point to "external sd/Resize_v22.4.1-signed.zip""
5. In one of following windows choose the partition size. I recommend between 8GB and 10GB. WARNING: If you choose less than the current size, you may loose your data. More than or equal to 8GB is a safe value.
Click to expand...
Click to collapse
Hi man Happy New Year . Can you upload again Resize_v22.4.1-signed.zip for Cube T8 Plus because the link not working....thanks

alex22280 said:
Hi man Happy New Year . Can you upload again Resize_v22.4.1-signed.zip for Cube T8 Plus because the link not working....thanks
Click to expand...
Click to collapse
I've taken the link from the first post here: http://forum.xda-developers.com/general/rooting-roms/guide-how-to-resize-data-internal-t3180978/ - see attached files, to get a correct link. I wouldn't reupload this. It looks like x-d is rotating attachment links.
Please edit your quotation so it does not contain wrong link.

maludroid said:
I've taken the link from the first post here: http://forum.xda-developers.com/general/rooting-roms/guide-how-to-resize-data-internal-t3180978/ - see attached files, to get a correct link. I wouldn't reupload this. It looks like x-d is rotating attachment links.
Please edit your quotation so it does not contain wrong link.
Click to expand...
Click to collapse
Resize_v23-signed.zip ?

alex22280 said:
Resize_v23-signed.zip ?
Click to expand...
Click to collapse
I assume it works as well...

[GUIDE to ROOT] for new users, step by step, main aspects clarified

INTRODUCTION (don't skip it if you want understand what you are reading)
Here we are, as promised.
A guide for beginners who hardly understand all the brief steps described in guides: root Galaxy S5 G-900V, unlock-bootloaders, etc. thanks for everyone who helped me with big patience (jrkruse, Bryanx86, XeCuTioN, youdoofus and all other guys) and who developed the scripts/guides. This guide is to help you keep focusing there
I'll try to be as brief as possible, remembering me when I entered in theis world without knowing this phone, and eager of flashing quickly the desidered ROM. I admit I've spent different days and a bounch bad words around figuring out all the obstacles that appeared time by time: you should know from the beginning that a small variation of the process described here may force you start from zero, loosing an amount of time, and that there are different phone models and also with different chipset, so you need carefully understand which phone you have before learning the process or losing time with wrong experiments, they will not work.
Anyway this guide will help many figuring out different aspects of phone, useful to everyone who is appraching flash the S5, it's a collection of important things I've read arond and experimented myself.
PHONE:
I have a S5 G900V with Toshiba chipset "CID11", and I tested all the following only on this phone, for questions/explanations read this article:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I'm not going to give any support to other versions, but post me if I forgot something
DEFINITIONS:
PHONE: unfortunately there are a moltitude of Galaxy S5 released, they are dedicated to particular geographic areas and particular service operators, the 900V is created for Verizon brand and it has a native ROM with SIM locked. If you bought one with SIM unlocked (and you may even read under "about" it is a 900F for example! check the right one starting the download mode) and you want root it/upgrade you should consider that the first rom uploaded to begin the following process is Verizion original, and it contains SIM lock: you will not use your phone later till you flash the final desidered rom! Chances are also, if you have like I do a CID11 chipset, the SD card will stop be recognized, and that's a boring thing. EDIT: the SD card will work, it was my phone with the SD gold contacts spoiled, accurately I lift them up and sd worked always later.
CHIPSET: as I know there are two variants around, one with Chipset Sasmung "eMMC" and one with Toshiba "eMMC". Before you start you need to read the file /sys/block/mmcblk0/device/cid under the root path, the first two bytes will be 11 or 15, if you have 15 you're lucky and you may even remove the locked bootloader, if you have 11 there are not solutions yet for unlock, but you can install Marshmellow 6.0.1 (unrooted/without root). To check the file CID I suggest to install xplore from Lonelycatgames (you may find a copy around, google it and download apk, open the folder root, the path /sys/block/mmcblk0/device/ and at file cid push long and use the hex editor.
BOOTLOADER: The Verizon phones accept ROMs only containing their certificate (it's more complex but let's say it's like that), they are called stock ROM (ROMs coming from brend, original, untouched). To load other custom roms you need to unlock the Bootloader to avoid checks on certifications, and this is possible only if you have a CID 15 and only after rooting phone, and unlock bootloader. Then you will you are able to flash TWRP which is a nice console for upload any kind of rom.
Anyway, anyCID, there is a "workaround" called Safestrap that loads a TWRP console instead of the classic Android operative system (OS).. and it happens when you will reboot from its Safestrap applications: the console will load instead of Android on next reboot, and when you will reboot from Safestrap console, itself will restores Android the next boot. It's the only way to load ROMS when your CID is 11, but only very particular releases (read about down); and the way to unlock bootloader on CID15. We're waiting that someone in future will unlock also the CID11..
the "bootloader" or "download mode" can be opened only from phone switched off by pressing VolDwn+Home and when u sure u're pressing them correctly then press power keeping them pressed(!) until u see the bootloader, press then volume up.
"recovery console" or "recovery" is reached from phone switched off in the same way, but pressing Volup+Home (the power) until u see the recovery.
ROM: it's a file containing usually the kernel, the system with main applications (excluded google apps), some scripts (commands) to cancel datas before installing.
GOOGLE APPS: you have to flash them after flashed the rom (if the rom asking explicitly for them because made without (it means it doesn't contain inside any google apps that may be crucial for booting), or.. you have to flash them if you're targeting the final result (the last flash) and you want have apps updated in your "new flashed phone". It's not necessary when u're in process of root phone/unlocking.
FLASH A BOOT IMAGE/package: it's a file used to replace the bootloader, when it's needed, for example if you are upgrading from Lollipop to Marshmellow the bootloader can't stay in lollipop version, the versions should match, be sure to have both compatible already downloaded.
ROOT: it means gain the administrators privileges to edit system files on phone.
TWRP: it's a smart console to manage the phone with full control, allows to change the Android versions and many other things.
RECCOMENDATIONS:
1) have battery on phone around 100%, looks because it seems that at lower values make the phone react sometime unexpectly (power safe) during operations, that means you may loose after a lot time to figure out what problem occured/process skipped.
2) During the flashing, in download mode, the phone may not be charged from USB, and the PC power is much less powerful then the charger, you may see a quite impressive battery draining even when connected to PC, this is why is better to start near 100%.
3) During update, the USB up/downs may use lot of CPU of your PC due to driver recognition, keep then your Windows "clean" for the process, no apps in backgroud which use lot of RAM and CPU (for example browsers with many tabs opened), so the driver detection could be faster, avoid programming interruptions (for example installing apps in root.bat)
NOTICE: any time u'll use Odin you don't need to change its flags/settings (for example auto reboot), leave them as they are. If you uploaded something wrong/not certifed under download mode and the phone refuses that, you need to switch off the phone and restart in download mode again, it's not up to software Odin in your PC; you can leave it opened.
Odin will check the checksum of files that are loaded, so for big rom files you have to be patient and give it time to read all file.
When Odin is open and USB connected, you have to see the phone connected by COM, if it doesn't connect the phone may be bricked or you have to install the latest Samsung drivers (!! **you can't forget installing them if it's the first time using a Samsung device!!)
HOW IT WORKS:
useful to understand how is reached the goal here to prevent bricks, solve easier problems, find yourself an overcome. This root kit targets to install 3 applications on the phone, then use a temporary "bricked" kernel to allow edit system files and root the phone before it loads all Android, then restore the previous kernel working, and it ends by using applications installed before to install Safestrap into boot, to have a TWRP console even if the phone is locked.
As the Safestrap substitute the normal Android boot, if there is any problem on the process (=Safestrap will not boot when it's supposed to boot = you started it from its application) the phone may brick here, because when Safestrap stars it need to restore Android normal usage: if it will hapen the Android won't load again, the phone is bricked, read in that section how to solve it.
The first application, Kingoroot,it's made for allow the root permission into other two applications, it's a supervisor. If you use it gently and its installation succeded ok in the beginning of root.bat it will be enough for do all the job (even if the main Guide author suggest to buy SuperSUme).
Busybox it's a software that allows Safestrap to install, whothout it Safestrap won't work.
Safestrap it's a simple application, that if used in right way (I failed lot of times, but I always recovered my phone) permits to have a powerful console on next reboot.
IMPORTANT:
Whne in process, wait always that the USB drivers finishing detecting phone and become "stable" (CPU and hard disk aren't working, keep check them to be sure, as well the icon of the phone should appear in Windows resouces). You may need to start from zero if u miss this, a really stupid reason to lose time.
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
PROCEDURE:
1) Open OK3_ROOT_V5.exe in one folder, if you use windows with particular language and not latin chars avoid to extract it on desktop, prefer a path like C:\galaxy for example.
2) Switch off phone, remove SIM card and SD, switch on in recovery mode and wipe data system and cache, then boot to bootloader
2) open Odin, open under AP G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 and wait until it finished read file, connect phone USB, be sure phone is recognized, start flashing. Wait until phone boots, wait until it shows the beginning screen.
3) choose english, then wi fi button down, then skip the connetcion and everything else asked, insert any fake name.
4) When setup ends don't activate Wi fi, go to settings, about, press 8 times build number, get the development menu active, go into it and enable usb debug, wait for popup and allow your PC always, then disable the verify usb application installation in the same menu. The driver may set itself again after this, wait some seconds befor go over and be sure the phone is seen by Windows resources, when you see the icon of the phone on Windows file explorer and the CPU is low again it's time to run root.bat, not before! Go into OK3_ROOT folder, run root.bat, a black old DOS window will open (this is not Odin! Not confuse this window and what you read there with Odin messages, please!) and follow the steps you read in this new DOS window..
it will install apps, reboot in download mode and show you a new Odin window, select NK2_kernel.tar and flash it, now put your eyes over DOS window of root.bat, it should recognize your firmware and after some seconds display a full page of ########, if it doesn't something went wrong, you need to go to recovery console, wipe everything, and flash again the main big flash (=start from zero).
If succeed, and you will read it in the DOS window, as the last step, you have to disconnect USB, pull battery, switch phone on in download mode and flash VZW_BOK3_KERNEL_ONLY.tar with Odin
5) After reboot open KingRoot application already installed, Click The Up Arrows a couple of time until you get to Try It and yes click Try It, then on the main circle, go back with arrow and you will have confirm that is rooted. Close Kingroot, open busybox free app, allow the root access, click on install (even if it start scannig) and wait some seconds, when it say it completed close it. Open Safestrap, allow root, click on install, the app will quit itself, open it again and click on install, it will quit again. Now reboot phone by the power key, hen rebooted open again Safestrap and now you'll be finally ready to click on the button "Reboot to recovery". Before doing it be ready to organize the next step, like files for unlocking bootloader or flashing a locked phone to 6.0.1.
END rooting phone procedure.
BRICK/RECOVERY: if it happens during root, before you upload any other ROM, there may be three ways to solve that:
Pull the battery out (it's almost safe) and:
1) Light: go under download mode and flash VZW_BOK3_KERNEL_ONLY.tar, see if the phones later boot up normally.
Chances are, with "dirty" chache data that lead the phone to brick, you can't start the root.bat procedure again succesfully (use root2.bat to avoid the install of the three applications that supposed already installed). Then you may try to:
2) medium: go under recovery console, wipe data and cache, boot fom there to download mode and flash again VZW_BOK3_KERNEL_ONLY.tar.
Or, if still not successful:
3) Strong: go under recovery console, wipe data and cache, boot fom there to download mode and flash flash full G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 (that means start from zero)
SAFESTRAP WORLD:
WARNING: you should follow at the letter the above process above, any difference may result in a fail of Safestrap recovery to open and phone bricked at samsung logo (+custom). If so don't worry, you have just to start the download mode and flash VZW_BPB1_KERNEL_ONLY.tar.md5 again to see the phone working. But chances you probably now have to repeat all the procedure from zero because your phone is "dirty" and Safestrap won't work more, proceed to what I called "strong" reflashing in brick section.
NOTICE: when you reboot to Safestrap, after Samsung logo, you need to wait 5-10 seconds to see Safestrap.
FLASH FIRE METHOD:
You may prefer to use FF (Flash Fire) to flash your room, it is a app (apk) that needs t be installed on phone when the phone works in normal mode, it allows you to create a list of different "orders" to execute exactly one after the other after you give it the final "ok". The app reboot the phone and starting itself to flash. It may be faster then Safestrap, but when I tried once it didn't work for me, it flashed partially and rebooted before it finished, I had a soft brick and I should restart from zero. Probably it was me pretending to flash something wrong, there is only one way to upload 6.0.1 on a CID11 phone and I did only once with Safestrap.
For dealing with FF you need the phone rooted, after you followed the process above you don't need to install Busybox, neither Safestrap, but you need to find and install SuperSUme.apk, which is another "root manager" program as Kingoroot is, but FF doesn't work with Kingoroot.
After loading kingoroot copy the Flashfire apk and SuperSUme in your phone, install both of them, start first SuperSUme, allow the root, and let it remove Kingoroot in its procedure, when it finished launch FF and let him the root as well.
You need to find these two apk, google them, since SUperSUme is available only paying you should know what you are doing. I used these versons and they worked: supersume-6.0.apk, flashfire-0-50-android-apk-download (notice there is 0.52, but I tested 0.50)
PS: if you feel this useful, please thank me pressing the button

For uploading 6.0.1 to my locked phone I folowed this guide:
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I would just add that having the SD card "not recognized" I simply copied files of ROM and GAPPS into the phone folder accessed by Windows resources. And when I reboot to Safestrap I flashed as last step the GAPPS, nothing more to add.
When you wipe Data you actually don't delete the /sdcard folder, so the ROM files are safe there.
if you accidentally delete files under safestrap you can upload them by adb, but it will be really slow (around 500KB/s), here is the command: adb push /path/to/local/filename.zip /sdcard/filename.zip
You may evaluate to flash also this before GAPPS:
Tethering_Fix_Knox_Removal_Slight_Debloat_V2.zip to remove Knox and useless apps from this ROM
If you need to put your default system language (the ROM is in english) download from google MoreLocale 2, open a DOS windows with the path to the folder of root.bat, activate the developer menu (point N°4 of post above), connect the USB, and type
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION

Do you know any details about the new pf4 modem?

no, Im not that expert, here is just a guide to help people into the process..

thank you for the great guide. I was able to root my phone with the clear instruction.
However, I am running into one trouble.
When my phone is setting up the language and etc, it requires me to insert sim or wifi. I can't skip that step without doing one or the other. When I do turn on the wifi, the phone then upgrades itself to android 5.0 but the root is still there. I am using T-mobile sim card.
Is there a way to get around the check up? I made sure to follow all the steps correctly too.

if u're talking about the first beginning steps, after the first big ROM loaded, yes you can skip. Select wi fi button, but after skip all the rest. I've never had to connect to internet or inserted a sim card for the process.
I connected/inserted sim only after the flash to desidered rom

thewebsiteisdown said:
Do you know any details about the new pf4 modem?
Click to expand...
Click to collapse
What kind of details did you want to know? Mine works fine.

Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this

Bryanx86 said:
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Click to expand...
Click to collapse
I added the FF guide

Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?

nachoalt said:
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
Click to expand...
Click to collapse
you didn't read well the first post. Read it back.

Barabba11 said:
INTRODUCTION (don't skip it if you want understand what you are reading)
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
Seems like the file name for OK3_ROOT_V5.exe changed. They call it GS5_LOLLIROOT.tar.gz now (must unzip twice to get all the files) but I looks like what is needed is in this zipped file.
Might take the plunge tomorrow so wish me luck, and thanks again for the explanation!

By "run root.bat" in point 4 do you mean "3 - Root Process.bat"?
Thanks for clarifications

Barabba11,
Since you seems to have a genuine desire of helping people, (and because I want to have my phone rooted), I want to comment your instructions and also try to find what I did wrong, since my phone is locked in the black “Samsung Galaxy S5” screen when trying to accomplish step 4 (no worries, I have been there before…).
Here I go…
FILES YOU NEED
Samsung Drivers: No comments here, straight forward thing to accomplish.
From the original post Here, under “Installing PB1”:
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
{
"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"
}
From the same previously mentioned post, now under “Rooting Instructions”:
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
Then, under “crc” folder you will find:
And finally, “System” folder is empty.
At this stage my series of comments:
1. I don’t see anything called OK3_ROOT_V5.exe mentioned in step 4 of your procedure. I assume you’re referring to the zipped file GS5_LOLLIROOT_BLACKCAT.7z but since almost every suggestion here indicates to read thoroughly, I don’t want to miss any detail. Can you please confirm if what you call OK3_ROOT folder is the unzipped GS5_LOLLIROOT_BLACKCAT.7z?
2. I don’t see anything called root.bat in the unzipped folders above, mentioned in the same step 4. Can you confirm which one of the .bat files are you referring to? Is it 1 - Install APK's.bat, 2 - Flash NK2.bat, 3 - Root Process.bat or 4 - Flash PB1.bat?
Since my phone got stuck in the black screen when reaching this point and I had to get back to square 1, I’ll wait for comments.
Warmest regards, it is really appreciated what you do here, it is just my humble opinion that detailed instructions in plain English, with proper file names, punctuation etc, would save this world a lot of time and frustration, leaving you developers more time to deal with the important stuff, I’ll be happy to help rewriting or reviewing anything in this regard.
PD: Not sure if the images are going to appear, I don't see them in the preview. If that's the case, you can check here

This thread is out of date since the rooting method has entirely been changed

Can you please indicate where can I find the updated method? Rgds

I'm sorry for the inconvenience, since they changed the main files I'm disoriented too. If they removed the bat files it means everything is different now, and honestly I'm hearing now about that..
Would know too why they changed the process, it was working, complicated but working, and I still have my phone at unrooted Android 6 waiting for a major update, like root or Android7.. I don't have enough time to experiment something that may appear useless for me later.
Anyway reading the instructions may warn you about different aspects to consider.. and reduce the waste of time if some conditions happened.
Kindly write in this thread they way you proceed and I'll have care to edit the first post reminding it. Thank you

Great thread, need some help still
How do I check my chipset when I don't have root access? I downloaded xplore but I need root access to check the root folder.

go into the xplore settings and change the root inside, I've no-rooted phone and I can see it. In the beginning, it's just a way for them to push you install rooting apps

If I root my S5 900V using this method can I then reflash it with 4.4.2?