Ace II X Development - Galaxy Ace II General

Ace II X Development - Galaxy Ace II General

THIS THREAD HAS NOT BEEN UPDATED FOR AWHILE. IF YOU HAVE ANY QUESTIONS ABOUT ANYTHING IN THIS THREAD, SUCH AS AVAILABLE CUSTOM ROMS OR KERNELS, PLEASE MESSAGE ME
The Samsung Galaxy Ace II X (GT-S7560M) is a Canadian variant of the Samsung Galaxy Ace II. The two devices have nothing alike except for the build. The Ace II X has a Snapdragon MSM7227A chipset (1 GHz Cortex-A5 CPU and an 'enhanced' Adreno 200 GPU), 768MB RAM (645MB accessible), 4GB of internal storage (1.8GB accessible), a 4" display, a 5 megapixel rear camera, a 0.3 megapixel front camera, and (the biggest difference is that it) runs on ICS 4.0.4 with Touchwiz Nature UX. The Ace II X is essentially the Galaxy S Duos (GT-S7562) but without dual SIM card support.
The purpose of this thread is to keep all the development for this scarce variant organized. Below is a list of things accomplished with the Ace II X:
1. Rooting
The purpose of rooting is to allow access to higher level permissions so that you can do more with your phone such as remove any junk apps (called bloatware) that are installed on the device by default, increase CPU clock speed (so the device runs smoother), change how the phone manages RAM, and more. As of now, there is no stock firmware dump, so once you root, your warranty may be voided. The root procedure involves flashing CWM recovery, then rooting via CWM.
To root your Ace II X (on Windows)
-Download the "root kit" here.
-Extract the files from the download once it is complete.
-In the folder Odin307, there will be a file called "Odin3 v3.07.exe". Double click on it, and it should open a program called Odin.
-Click the button 'PDA' (on the left of the window) and select the file 'recovery.tar' (that should be in location where you extracted the root kit).
-Make sure that only 'Auto Reboot' and 'F. Reset Time' are checkboxed in Odin.
-Power off your Ace II X and hold down the power button, the home button, and the volume down button all at once.
-Press the volume up button and connect your phone to your computer with the USB cable that was included in the packaging for your Ace II X.
-A box in the top left of Odin called 'ID:COM' should turn yellow.
-Press start and your device will reboot when it is done.
-Power off your device and hold down the power button, the home button, the volume up, and the volume down button all at once.
-Let go off the buttons immediately when the 'Samsung Galaxy Ace II X GT-S7560M' logo appears.
-Transfer the file "CWM-Superuser_1.0.1.7.zip" to a micro sd card, and put the micro sd card in your device.
-Select 'Install zip from sdcard' (in CWM recovery) using the volume keys to scroll up or down and the home button to select an option.
-Select the "CWM-Superuser_1.0.1.7.zip" that you put on your micro sd card earlier.
-Wait a moment or two and your device will be rooted! Enjoy!
NEW METHOD OF ROOTING FOUND. This new method involves using a program (Windows only) called UnlockRoot. Follow the instructions found there to root without increasing the flash counter (yellow triangle) or getting rid of stock recovery. Stock recovery can be found here for those that have rooted using the root kit.
2. Remove the Yellow Triangle At Boot
Once you root, a yellow triangle will appear on the bottom of your screen whenever you turn on your phone. This happens as a result of rooting, and it shows that your device has been modified. Removing the triangle requires a simple application.
-Download the application Triangle Away from the bottom of the first post of this thread.
-Transfer the file to your micro sd card.
-Go to the Settings app, Security, and select 'Unknown Sources' to allow the installation of non-market apps. Click OK on the box that pops up.
-Using the My Files app (comes with the device), navigate to the external sd card and select the .apk file that you transfered to your sd card earlier.
-Click 'Install'
-It should install. Open it.
-Grant the app 'Superuser permissions'.
-Select 'Reset flash counter'
-It should make the yellow triangle disappear. Enjoy!
3. Deodexing
Stock ROMs are odexed, meaning that each system application (.apk) is split into two parts: The .apk and the .odex. An odexed ROM takes up less space and is a bit faster because its .dex files are optimized, thus making .odex files. A deodexed ROM means that the two parts are assembled into a single file (.apk). A deodexed ROM takes up more space (a bigger dalvik cache) but allows for more modifications. The /system/framework folder must always be completely deodexed or odexed, but the /system/app folder can be partially deodexed (if the framework folder is odexed). Anyways, I have deodexed the stock ROM and made it into a CWM flashable package.
- Download the two .zip files from here and here.
- Place the two .zips on your external sdcard.
- Power off your phone and boot to recovery mode.
- First install the OdexRemover.zip.
- Once it finishes, immediately flash the StockDeodexed.zip.
- Reboot, and you're done!
4. Kernels
Kernels are essential. Packed in a boot.img file, a kernel is the link between the hardware and the software. It basically controls your device's CPU speed and RAM management. The problem with the stock kernels are that can cause lag, or slowdowns. With a custom kernel, you can freely raise or lower the fixed clock speed to get better performance or save battery power. You can also change how the device manages Random Access Memory for a better and smoother experience. Currently, there are only a couple kernels available:
- Stock Kernel (Insecure) by Codename13
- KyleOpen Kernel (Original by cheatman) ported by SeannyM
-
Instructions for installing one of the following kernels is as follows:
- Download the file.
- Using Odin, simply refer to the instructions for rooting the device, only use the kernel.tar.md5 file in the PDA section (instead of the rooting kit)
- Boot your phone to download mode, plug it in to your computer and click start!
- Wait a moment until the operation is completed.
I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY NOT FOLLOWING THE INSTRUCTIONS PROPERLY. PROCEED WITH CAUTION WHEN FLASHING A KERNEL AS IT IS A VERY SENSITIVE PART OF THE DEVICE. YOU CAN BRICK (BREAK) YOUR DEVICE IF A KERNEL IS MISFLASHED.
5. Modifications
Probably the best part about rooting is that you can modify your device however you want. I have merged several mods that I have done on the device into a single package. Install the file found in the link here
using Clockworkmod Recovery mode. The current mod compilation, Mod Pack II X v0.4, adds several mods. The list can be found in the linked page. The link will be updated when a new mod pack is released (no ETAs please).
TO BE CONTINUED (WHEN I HAVE MORE TIME)
Please do not use this thread as a discussion. Use this thread as a discussion. Only post in this thread if you have comments or questions related to anything in this main post.

Partition Table
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/modem emmc /dev/block/mmcblk0p3
/boot emmc /dev/block/mmcblk0p8
/persist ext4 /dev/block/mmcblk0p11
/recovery emmc /dev/block/mmcblk0p12
/dev/block/param /dev/block/mmcblk0p13
/system ext4 /dev/block/mmcblk0p16
/cache ext4 /dev/block/mmcblk0p17
/efs ext4 /dev/block/mmcblk0p19
/misc emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p22
/data ext4 /dev/block/mmcblk0p25
Click to expand...
Click to collapse

## This post is where you can find older things from my signature (such as links) that I no longer wish to or have enough space to keep in my signature ##
>CM10.2 custom ROM
>Enable Ripple Effect on Samsung ICS ROMs
>Install Ubuntu 13.04 with Wubi!
>BA2X 2.0 kernel for stock ROM
>Mod Pack II X for stock ROM

~reserved~

unlock
[Q] Is there a way to unlock the sim network providers?

Related

[9001][GUIDE][NOOBFRIENDLY]Starter-Guide[STOPPED]

I´m not responsible for what you do! This guide could “destroy” your phone if you do something different how it is explained!!!
I do not have any claim of fullness! If here should be any mistakes feel free to correct me!
Support is now stopped, read this post for more details...
Hi folks
I saw that here is missing a basic guide for our device, then I noticed that we have get a lot of new members, too!
This guide will be so noobfriendly that even my grandmother will understand it
I will try to answer here every question and I will add it then to the front page. I will answer very kindly, too! So feel free to ask everything =)
Please follow each step, don´t skip any step and do all exactly how I explain it...
Must haves:
Following things are must haves for every I9001 phone. In this guide I will explain how to get them on YOUR phone.
Most things will be installed automated by a installation of a custom rom, which is then more easily for you to get them!
Busybox
USB-Debugging
Clockworkmod
Root
Deodex
1. Basics:
About Roms:
What is a Rom:
The whole system of your phone is a rom. Windows 7 is a Rom for your computer (just a metaphor)
A rom contains different sections:
boot.img (kernel)
system.img (the main-system)
recovery.img (recovery mode)cache.img (caches)
Stock-Rom:
The Stock-Rom is the system which Samsung is delivering to the store. Samsung built this rom from the google sources and changed android they way they like it.
The stock-rom is the original rom of your phone!
You can find a lot of stock roms in the Index or just here in the dev forum
Custom-Rom:
A custom-rom is a modified rom which has different improvements. The base can be of a stock rom or it is an AOSP-Rom.
You can find a lot of custom roms here in the forum or just visit the Index
AOSP-Rom:
This is a Custom-Rom too, but the base is built from the sources of Google. The advantages are that there is not any garbage, it is more stable and it has more functionality. But the disadvantage is that it is hard to build and it will take long time for being bug free.
Basic knowledge:
What are Tweaks:
Tweaks are changing values in the system. Tweaks ussually improves the whole system
Kernel Description:
The Kernel is a piece of software which controls everything on your system.
The kernel controls the cpu with the governor. The governor decides the behavior of the cpu, like when the cpu has to be on the max. clock or when it has to be on the min. clock.
The kernel controls the ram and sd-card behavior with the scheduler. The scheduler decides how long a process should be saved in the ram and it influences the sd-card read and write speed.
The kernel controls the voltage of the battery on a specific cpu clock, too
The kernels which are offered here are oc (overclocked), UV (under volted), they add new governors and scheduler and the add the init.d support.
Init.d makes it possible to launch tweaks at the boot of the phone if they are in the init.d folder (system/etc/init.d).
A description of governors and scheduler are here and here
You can change the governor and scheduler with AnTuTu CPU Master
I recommend strongly to change the kernel because it improves your system immense, but in the other hand the car cardle will not work anymore with these kernels.
Only Stock Kernel and the stock kernel with init.d support the car cardle
At the moment are following kernel popular:
Skyhigh
Feamod
Vitality
Stock Kernel with Init.d - KQ7
Bloadware:
Bloadware are apps which nobody needs. Samsung implement them in their stock roms. When they are removed there will be more free space for other apps and more ram will be available
Brick:
Your phone is bricked when it can not boot anymore.
There are two types bricks
Soft Brick:
When your phone is soft bricked it can cause a boot-loop (the reboot-procedure begins always as new) or your phone will stick in the boot.
Soft bricks happen often by installing themes over a odex system (more informations in the 8. point)
You can solve soft bricks easily by installing a new rom with the clockworkmod or with odin (more informations in the 2. point)
Hard Brick:
When your phone is hard bricked it will not do anything. You will not be able to enter the clockworkmod or the downloadmode!
Hard bricks often happen by flashing roms of other phones or flashing bad custom roms (at the moment there aren´t any "bad" customs roms for our device)
You can solve SOMETIMES a hard brick with a JTAG. If the jtag could not help you have to send your phone to samsung for a expensive repair
Batterly life:
You can improve your battery life by changing the governor, the scheduler, turning off gps, bluetooth, wi-fi and by changing the brightness of your display.
You can improve your battery life too by changing the max. and min. clock of your cpu. But here is to say you have to find your personal middle way of performance and battery life settings.
Wipe:
A wipe is when you delete everything on your phone. It has the same meaning as "format" and "delete". How to wipe your phone is explained in the 6. point
Other Settings:
Animations:
In the default settings the animations are diactivated, but they look so nice that you have to activate them . If you want for example the old screen off you have to activate the animations.
How to activate animations:
Enter in the settings of your smart-phone
Select "display"
Choose "animation"
Choose "all animations"
Wi-Fi troubles:
If you face Wi-Fi troubles could this method solve your problems
Enter in the settings of your phone
Choose "Wirelless and network"
Choose "Wi-Fi settings"
Press the Menu-Button
Choose "Advanced"
Activate "use static IP"
Busybox:
Busybox is a collection of commands and functions for every android phone. Some custom roms will even not be working properly without Busybox! Normally Busybox will be installed automated by a custom rom installation , but if not you can install the .zip in the post #3 through Clockworkmod (detailed explanation for installing .zips with clockworkmod are in the 2. Point)
USB Settings:
What is USB-Debugging:
USB-Debugging is a function of Android. If it is enabled you will be able to use adb. Make sure that you have it always enabled because you will need it often and by the way it does not have any disadvantages
What is adb:
adb means: Android Debug Bridge
With adb you can change/edit/install files on your phone with your computer. Broodplank1337 made a big configurator which can do incredible things!
Configurator
How To use Adb is explained in this Tutorial
How to enable USB-Debugging:
Enter in the settings of your phone
Enter in the “Applications”
Enter in “Development”
Enable “USB-Debugging”
How to copy files on your internal SD card:
Make sure that you´ve got at least installed the USB Driver if not download them from the download section (if you have installed kies you got the USB Driver installed too)
Make sure that you have enabled USB-Debugging in the Settings of your phone
Connect now your device with your computer with the usb-wire
Now just pull down your status bar and select the usb notification then you choose "connect storage to PC"
Now you can copy files on your internal SD-card
Your internal SD-card is the storage with 5 GB
2. How to install every Rom/Kernel/Recovery/Mod:
General
If it is a zip file you have to install it with Clockworkmod Recovery. If it is a .tar or a .tar.md5 file you have to install it with Odin!
Odin:
What is Odin:
Odin is a program on windows where you can install custom roms and kernel during your phone is in the Download Mode. To use Odin you need the AriesVE.ops and the kernel or custom rom you want to install.
What is the Download Mode:
When you phone is in the Download Mode you will be able to flash kernel, roms, new recovery modes with Odin. You can only exit the Download Mode by taking of the battery or when odin finished flashing!
How to get in the Download Mode:
Please turn off your phone and wait until it is completely shut down
Press the Home-button + volume-down + power button until there is an android icon
(In post#2) is a Imagine which could help you)
Installing Custom Roms and Kernels with Odin
Download:
Odin
AriesVE
(downloadlinks are in post#3)
Start Odin.exe
Press on "OPS" and choose the AriesVE.ops
Activate the Option "One Package"
Click on "One Package" and select the .tar or .tar.md5 file
Put your phone in to the download mode
Connect your phone with the usb-wire
Press "Start" in Odin
Wait until your phone reboots automatically
(In post#2) is a Imagine which could help you)
Recovery-Mode:
What is the Recovery Mode:
The Recovery Mode is like the BIOS of your computer. There you can manage your phone easily. The Stock Recovery Mode does not have a lot of functions, because of this there were made new recovery mode by good devs. A better recovery mode is the clockworkmod
What is the clockworkmod:
The clockworkmod is actually the most popular recovery mode. At the moment it is the most stable one, too
Other expressions for "clockworkmod":
"CWM"
"Recovery Mode"
"feamod"
What are the differences between Stock-Recovery Mod and Clockworkmod:
With the stock Recovery Mod you can just make a Factory Reset and install simple zip files. You will not be able to install custom roms!
With the clockworkmod you can backup, restore and format your system and install any custom rom
Do I need the Clockworkmod:
Yes it is a must have, you will not be able to install any custom rom or other mods
How to get in the stock-Recovery Mode:
Please turn off your phone and wait until it is completely shut down
Press please the power + the volume up button for 10 seconds
When you see a Box with an android icon press once the menu button to be able to use it
How to navigate in stock Recovery Mode:
Navigating:
Volume Up/Down
Selecting:
Home-Button
How to install the Clockworkmod:
Download:
AriesVE
Odin
FeaModRecovery 1.2
(downloadlinks are in post#3)
Enter the Download Mod
Now start Odin
Select as always AriesVE.ops as ops file
Then activate “one package” option in Odin and choose as “one package” “FeaModRecovery_1.2.tar.md5”
Press "Start" and wait until your phone reboots
How to get in the Clockworkmod:
Please turn off your phone and wait until it is completely shut down
Press please the power + the volume up button for 10 seconds
How to navigate in Clockworkmod:
Navigating:
Volume Up/Down
Selecting:
Menu-Button
Back:
Back-Button
What is "mounting":
If you mount something you will be able to edit/delete/add files to your system. Developer always recommend to mount /system before installing a mod, because if you don´t do it the mod will not be installed successfully
How can I mount /system:
Enter in the Clockworkmod
Choose "mounts and storage"
Choose "mount /system"
It works with /data , /cache , /efs , /emmc , /sdcard ,too
How to install Custom Roms/Kernel/Recovery/Mods with the Clockworkmod:
Put the zip file on your external-card in a folder (Do not put it in a folder with starting with a ".")
Enter in the Clockworkmod
Choose “install zip from sdcard”
Choose “choose zip from sdcard”
Choose the .zip file and install it
Reboot
3. Root:
What is a Root:
You can compare "Root" with the "admin" on your computer or with a “Jailbreak” for Apple products. If you have "root" you can modify all on your system. If you have installed root there will be no more borders.
Other expressions for "root":
"superuser""su"
What can I do exactly with a Root:
Firstly you can backup your apps (will explain this later more precise)
You can change the cpu frequency (cpu=processor an electronic circuit which executes computer programs)
You can run every app which needs root access
Does the root pay up:
Yes it does because it is the first border to cross for having the best of your phone
How to install Root with Clockworkmod:
Download the root from post#3
Put the root.zip on your external-sd-card in a folder (Do not put it in a folder with starting with a ".")
Enter the Clockworkmod
Choose "install zip from sdcard"
Choose "choose zip from sdcard"
Choose the root.zip and install it
Reboot your phone
How to install Root with stock Recovery:
Download the root from post#3
Put it on your internal SD card. Please just copy it on your SD-card and NOT in any folder
Enter in the stock Recovery Mod
Then you choose “apply update” and you choose the root.zip and install it
Reboot then your Phone by choosing “rebooting”
How to Unroot:
Download the "unroot.zip" from post#3
Put the .zip on your external-sdcard in a folder
Enter in the clockworkmod/stock recovery mode
Install it like you installed the root.zip
4. How to Backup:
There are two ways of backing up your data.
With Titanium Backup:
Titanium Backup is an app which will only backup your apps
Titanium Backup is a free app but I recommend only the pro version, because the free is too slow
Your backup will be saved on you internal-card in:
/titanium backup/
With Clockworkmod:
With the clockworkmod you can backup your apps and your whole system with all settings. I prefer this method because it is simple and secure...
How to Backup in CWM:
Enter the Clockworkmod
Select “backup and restore”
Select “backup” and enjoy your backup
Your backup will be saved on your external-card in:
/clockworkmod/backup/
5. Restore:
How to restore the whole system:
Enter the Clockworkmod
Select “backup and restore”
Select “restore” and choose the date of your backup
How to restore only apps:
Before restoring you should always format your device! How to format is explained in the next point!
Enter the Clockworkmod
Select “backup and restore”
Select “advanced restore”
Choose the date of the backup
Choose “data”
6. How to format:
Do this every time before flashing a stock- or custom-rom!
Attention!
You will delete everything on your phone! Your phone will not even be able to boot! Only Clockworkmod and the Download-Mode will be left! (Your SIM-Card will be untouched)
Please make sure that you saved only your backups on another device before formatting your phone (like on your computer)
This is the best method for using the full experience of every custom rom! I recommend this method because in the past a lot of users had issues with custom roms. They had installed a lot of different custom roms before and they didn´t format their phone correctly before flashing the new rom. This caused a lot of problems
Enter in the Clockworkmod
Choose "advanced"
Choose "Wipe Dalvik Cache"
Go back to the main-menu by pressing the back button
Choose “Mounts and storage”
Select all after all
Format /system
Format /cache
Format /data
(Format /emmc)
(Format /sdcard)
Formating "emmc" and "sdcard" is not a duty! You will need it if you installed a mod on your internal or in your external card
7. Warranty:
What makes your warranty dissapear:
Root
Clockworkmod
Custom-Rom
Other Kernel
How to restore your warranty:
You can restore warranty easily, you have just to flash the stock-rom which was on your device when you bought it. If you not remember which stock-rom you had installed as first visit Sammobile and search for I9001. Download the stock-rom which is for your country, flash it with odin and you will have your warranty back
(For using the Search you have to Regist on Sammobile)
8. Deodex(ADVANCED):
What is Odex:
All apps are at the beginning odexed. Odex means that the apps are actually "packed". When the apps are odex it is more difficult to modify them.
What is Deodex:
Deodexing apps means that you are "unpacking" the apps. When you deodex your apps you will be able to modify them. A deodexed Rom belongs to basic because you will need it for installing a theme or other mods.
Deodexing your rom will not cause any disadvantages
How to Deodex:
Requierments:
Root
Busybox
Java SDK (Download is in the post #3)
USB-Debugging
xUltimate-v2.3.3 (Download is in the post #3)
Connect your phone with the usb-wire
Extract xUltimate-v2.3.3.zip
Start the "Test.exe"
Following must be in the command prompt:
adb = PASS!
odex = PASS!
zip = PASS!
busybox = PASS!
java = PASS!
temp = PASS!
deodex = SKIP!
redex = SKIP!
If something is different please do not deodex you phone because you will fail. If it all matches do following things:
Start the "Main.exe"
Press "1"
When it is finished press please "2"
Enter the folder "origi_app" and delete following files:
Maps.apk
Maps.odex
Phonesky.apk
Phonesky.odex
PlusOne.apk
PlusOne.odex
Enter again xUltimate-v2.3.3 and press please "3"
When it is finished press please "4"
After it is finished start the Deodex.bat (big thanks to nikagl for the commands)
After the automated reboot your phone should be successful deodexed
To check if youre phone is deodexed just run again the "Test.exe" and under the point "deodex" should be "PASS!" or under the point "odex" should be "FAIL!"
Other Tutorials:
How to install CM9 by Arco (alpha2):
Original Post
This tutorial only works if you have installed a custom recovery! How to install a custom recovery (clockworkmod) is explained in the Starter-Guide.
Please make sure that your phone is formated before doing this! How to format is explained in the Starter-Guide ,too.
1. Download please CM9 by arco
2. Unrar
3. Put the folder "2012-05-12.19.54.06" in "clockworkmod/backup" (internal or external is equal)
4. Put your phone in the recovery-mode
5. choose "backup and restore"
6. choose "restore" or "restore from external card"
7. choose "2012-05-12.19.54.06" and confirm
8. reboot
Do following if you do NOT have installed the Clockworkmod by Arco!
9. Download Arco´s Clockworkmod
10. Put your phone into download mode
11. Start Odin
12. Select the ops file
13. Check "one package" and select as "one package" "recovery-clockwork-5.5.0.4-ariesve.tar.md5"
14. Press "Start"
How To Connect both Storages at the same time on pc with CM9:
Original Post
So found an other solution where people were complainig off!
First big thanks to Campi1995 who tested it as well
So the problem was following:
people were not able to connect two storages at the same time with their computer and I found an interesting app in the market, it is called Multi Mount Sd-card
For mounting both storages do follwing things:
Install Multi Mount Sd-card
Add the Widget off the app on any homescreen (in the app drawer, you can add widget)
Connect your phone with the usb-wire
Click once at the widget (it should get green)
and BUUUUFF both is connected to the pc
Remember the pay app is better, but the free one works as well.
If there are any questions regarding this post feel free to contact me...
and again:
peace out fabsau
How to mount your external card on /sdcard/external_sd instead of /emmc/ on CM9
Original Post
Ok guys, after a lot of people were complaining about that the external sd card is now mounted as emmc (including me), I searched a little bit in the forum and I want to share what I´ve found!
Tintenfisch wrote a nice tutorial to make you happy, I tested it and it is working.
Tutorial
Just do what he say and you will be able to use your sd-card as external sd-card
(I activated "Alternate dbase mgmt", because tintenfisch it is recommending it, then I deactivated "Handle USB Connection")
Hoped I helped some people, if there are any questions regarding this post feel free to contact me!
peace out fabsau
How to add toggles on your notifaction bar
Original Post
1. Enter the settings
2. Click on System
3. Click on Notification Drawer
4. Click on Widget buttons and select your toggles
Credits:
KeksKlip - For the root
manveru0 - For the clockworkmod
Skywalker01 - For making big improvements in this forum (and later for the new clockworkmod)
All people which gave me this knowledge!! ♥
All other Devs that are working hard just to make US happy!!!!
Other Threads:
Index
Wiki
Quick-Flasher
Please remember that the Quickflasher is very noobfriendly and easy to use, but in my opinion you should use this tool if you know how to do the usual way (like it is here explained)

Screenshots
Buttons:
{
"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"
}
Download mode:
Odin (Ready for flashing):

Downloads
Downloads
USB-Driver
Busybox
AriesVE
Odin
FeaModRecovery 1.2
Root
Unroot
Java SDK

fabsau said:
7. Warranty restore:
You can restore your warranty easily! You have just to flash any stock rom via Odin for getting your warranty back and do not change anything!
Click to expand...
Click to collapse
Hm.. don't you need exactly the same ROM version of what your phone was before flashing or what your carrier offered you with KIES?

annqx said:
Hm.. don't you need exactly the same ROM version of what your phone was before flashing or what your carrier offered you with KIES?
Click to expand...
Click to collapse
some people buy their phone as sim unlocked (not carrier related) , and those are usually shipped with one of the stock roms available on sammobile . for the rest of us who got their phone with carrier bloatware, we need to have a backup of that stock rom.
as for this thread, although i support any help for people who are starting with android or are new to the device, but i pretty much don't see something that is not covered in the wiki. (not hating, just saying).

You enter STOCK RECOVERY by pressing vol up and power, and then MENU, not just vol up + power

more info
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001 don`t forget to add 9001`s wiki page you can put it on top of your tutorial because LOTS of ppl don`t read it

rayiskon said:
some people buy their phone as sim unlocked (not carrier related) , and those are usually shipped with one of the stock roms available on sammobile . for the rest of us who got their phone with carrier bloatware, we need to have a backup of that stock rom.
as for this thread, although i support any help for people who are starting with android or are new to the device, but i pretty much don't see something that is not covered in the wiki. (not hating, just saying).
Click to expand...
Click to collapse
I get your point and I understand you completly, but like I said in the thread more things will come...
glava34 said:
You enter STOCK RECOVERY by pressing vol up and power, and then MENU, not just vol up + power
Click to expand...
Click to collapse
Well I just descriped how to enter in the stock recovery, but I forgot to say how to "activate" it. so your I will add the menu-button thing
chasemyass said:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001 don`t forget to add 9001`s wiki page you can put it on top of your tutorial because LOTS of ppl don`t read it
Click to expand...
Click to collapse
This is a good idea I will do this...
Can someone explain how to restore the warranty because I´m the opinion that every stock-rom is enough. (I will ask some friends too)

fabsau said:
This is a good idea I will do this...
Can someone explain how to restore the warranty because I´m the opinion that every stock-rom is enough. (I will ask some friends too)
Click to expand...
Click to collapse
it`s written on wiki and actually is pretty simple just wrote down what ROM you got on your brand new SGS+, then download the correct version of it from web and put it safe....just in case you need it

Nice tutorial man ^^ You really explained a lot!

so guys added a lot of new things! few guides are under construction and I have to rework 7. point but I think I will finish this project on the 08 april, so stay tuned =)

so guys I finished the guide. If someone becomes troubles with something feel free to contact me!

Stickied!

fabsau said:
so guys I finished the guide. If someone becomes troubles with something feel free to contact me!
Click to expand...
Click to collapse
I would add @kernels the stock one with init.d support since it's the only one (beside pure stocks) that is working with car cradle
Sent from my GT-I9001 using Tapatalk 2 Beta-6

chasemyass said:
I would add @kernels the stock one with init.d support since it's the only one (beside pure stocks) that is working with car cradle
Sent from my GT-I9001 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
thanks for the information!
Because people now will ask what init.d is, I added a description of it, too

Hello
How I can remove clockwork mode installed with this ways?

Moonart said:
Hello
How I can remove clockwork mode installed with this ways?
Click to expand...
Click to collapse
at the moment only by flashing a stock rom...

Moonart said:
Hello
How I can remove clockwork mode installed with this ways?
Click to expand...
Click to collapse
you can dd the stock recovery.

unable to update after flashing custom rom
I'm having this problem: after flashing a custom rom from sammobile I'n unable to update in KIES. The strange thing is that I get for example XXXKQ7/DBTKP2/XXKPK/ and then the last numbers are of the firmware that previous was on the phone. I think I am doing something wrong but I simply don't know what. Can anyone give me a sollution for this.

Chicane301 said:
I'm having this problem: after flashing a custom rom from sammobile I'n unable to update in KIES. The strange thing is that I get for example XXXKQ7/DBTKP2/XXKPK/ and then the last numbers are of the firmware that previous was on the phone. I think I am doing something wrong but I simply don't know what. Can anyone give me a sollution for this.
Click to expand...
Click to collapse
Kies won`t let you upgrade everything ... the CSC code it`s the main rom chooser then. And not all released stocks are available to upgrade using Kies on ANY other stock

[guide]for noobs!!(includes everything to make you not a damn noob anymore):)

Your a noob and need help then dont worry this guide will help you
ALWAYS UPDATING(STILL NOT COMPLETE)
Android Dictionary
If you're new to Android, you are likely seeing a lot of unfamiliar words being thrown about... from CID to RUU to ROM. This dictionary will help you understand what these words actually mean, and when you would expect to see them.
ADB
ADB (Android Debug Bridge) is a PC command-line tool included with the Google Android SDK. ADB provides an interface for managing and debugging a USB connected Android device. Common ADB tasks include: *Collecting a log via logcat* Installing APK packages* Pushing or pulling files* Accessing the device shell.
For additional details about ADB please see the ADB guide.
APK
An APK is an Android application package (Android Package). It is commonly used to store an app, or program run on the device. These files are essentially zip files, in that they contain other files which make up the program. They can be obtained through various methods, such as installing an app through the market, downloading from a website, or creating yourself in Java. If you have an apk file on your computer, and wish to install it on your phone, you can run the command 'adb install apkname.apk' to copy the file over USB to your phone.
The APK files reside on the phone in the directory /data/app/filename.apk. This directory is not normally accessible unless a #root|rooted ROM is used on the phone, in order to protect paid-for applications. On a rooted ROM, it is possible to copy applications manually into this folder using the command 'adb push' or similar. Once a file is in the /data/app directory, it is installed on the phone. There is not normally an installation process for apps on Android.
It is also possible to install an app to the system partition of a rooted phone. This has the added benefit that the application cannot be uninstalled from the device, making it useful for security/anti-theft applications such as WaveSecure and MobileDefense. These [[#system]] applications are stored in /system/app. The applications in this folder are normally part of the Android operating system, and should not be modified or deleted unless you either put the file there yourself, or know what you are doing.
APK files can be uninstalled using the market application (if the application was installed from the market), the 'adb uninstall apkname.apk' command, the Settings | Applications | Manage Applications menu, or by manually removing the files from the /data/app directory as a last resort. Normally, the preferred method is through the market or applications menu.
Bart
Bart is used from Recovery to backup your phone or to restore a backup.This basically creates an exact copy of your phone (Sdcard + Sd-Ext excluded, unless it says it will backup SD-Ext), which later can be restored with no losses in data.
Boot
In contrast to other linux-based operating systems, Android has a boot partition (containing the contents of a boot.img file), as opposed to a direct booting system. This partition contains a read-only 'ramdisk', and a couple of other files. The ramdisk contains files critical to booting, such as init.rc and default.prop. This 'partition' actually sets up the directory structure of the device, having empty folders for /data, /dev, /proc, /sbin, /sys and /system.
Bootloader
The bootloader, or HBOOT, is firmware on the phone which runs on every startup.
Since the bootloader controls access to Fastboot, it can be desirable to change the version of the bootloader on a phone. The current version of the bootloader can be viewed by entering bootloader mode. To do so, turn on the phone with the back button held down. Release the back button after about 1 second. The version information will be displayed at the top of the screen next to the word HBOOT, and will appear in the form 'V1.76.0004' or similar.
From within the bootloader, Fastboot can be used to execute an img file stored on your PC or flash an img file to the device.
If your device has HBOOT version 1.73.007, it is no longer possible to use Fastboot, so it is often desirable to downgrade the HBOOT using the Goldcard method in order to get the 1.73.004 version, which is Security-Off, allowing Fastboot.
CID
The Carrier ID is a number embedded in your Phone's SPL that identifies what if your phone is a network branded Hero. For example, T-Mobile UK phones have a different CID to generic HTC phones. The CID prevents you from [[#Flash|flashing]] an 'incorrect' [[#RUU]] to your phone. Note that the RUUs will all function on any of the phones, but the CID locking prevents you from 'debranding' your phone by installing a generic [[#RUU]]. Additionally, the CID-related software also prevents you from installing an older RUU than what you are currently running.
It is possible to bypass the CID check on an [[#RUU]] using a [[#Goldcard]]. This pretends your phone has the 'Super-CID', which allows any branding of ROM to be installed, and allows you to downgrade the software on your phone.
Data
The data partition on the device contains the user-related data, such as installed applications and settings for those apps, as well as your SQLite database containing Android settings and messages. Normally, the directory /data/app is off-limits through the 'adb shell' command, as well as other terminal applications that can run on the device, since this directory contains the apk files for apps. On a rooted phone, using the [[#su]] command will allow full access to this partition. This partition can be flashed using Fastboot or Nandroid.
Ext
Ext is an abbreviation of the extended filesystem, one of the filesystems supported by Android and other Linux based systems. An ext filesystem partition is required for using Apps2SD or Dalvik2sd.
Fastboot
Fastboot is a means to execute or Flash an img file on your device. First, set up your PC for ADB, and ensure that it works correctly. After putting your phone into Bootloader mode, and selecting Fastboot by pressing back (if you let go of the back key early), the device awaits a command via USB.
On your computer, execute the command 'fastboot devices', which should display your device serial number. This confirms you are ready to use Fastboot. To execute (ie. run without changing your system) and img file, type the command 'fastboot boot imagename.img'. This command allows you to run a custom recovery image without flashing it to the device.
If you wish to flash an img file to the device, the command 'fastboot flash IMGTYPE imgtype.img' should be used. Note that IMGTYPE should be replaced by the type of img file you are flashing. For example, to flash a recovery image, the command 'fastboot flash recovery patched_recovery.img' should be used. The following are valid types of image to flash; boot, recovery, system,
Flash
Flashing is the process of writing data to the internal memory on your phone. Normally, you would flash a [[#ROM]] image to the phone, which would give you a different version of system software on your phone. Flashing can also refer to updating/writing to any of the other parts of the phone, such as the SPL, Radio etc.
Flash Memory
Flash memory, also known as NAND memory, is nonvolatile - keeping information even when the device is off. Flash memory in the device is equivalent to the hard drive in a computer. This is where the device's operating system (sometimes called firmware) and applications are stored. Flash memory is slower than RAM, but is (almost always) faster than SD cards.
Flashrec
Flashrec is an application/tool you use to flash the recovery image to your phone. (Found on http://zenthought.org/content/project/flashrec)All current firmwares are patched so you can not use flashrec on these, you will receive the error message "Could not run command"Most 1.5 (cupcake) firmwares can still use this, but some has been patched already.The current version is 1.1.3 and was updated 2009-08-16.Note: Do not flash cyanogen's theme templates after you have started the installed recovery image, this will brick your phone!
Goldcard
A goldcard is the name given to a specially modified microSD memory card for your phone that allows you to install software to your phone that is in an RUU file, but not from the same network provider as your phone is from. It does this by bypassing the CID check of the RUU update. Additionally, the goldcard allows you to install an earlier version of system software onto your phone than what is already on it (called downgrading). This can make it easier to root a phone and install a custom ROM on it, if the software installed on it at present cannot easily be rooted.
HBOOT
See Bootloader.
logcat
Using adb (see ADB), type in "adb logcat >logcat.txt". This will help us when resolving issues and bugs.There is also a tool in the market you can use for this, called aLogcat. It can show different categories (severity of errors ect.) too, adb logcat can not do this.
Market
The market on Android is a place where you can purchase or download applications for your phone in the [[#APK]] format. When you download through the market, the installation process is transparent (as in you don't have to deal with the APK files yourself), and there is the facility to rate apps and post comments which are visible to other users. Frequently, the developers of apps actually take onboard the feedback in the comments (mainly the smaller apps with slightly less feedback to sift through).
When an app is installed from the market, it is copied to '/data/app/apkname.apk', as the act of 'installing'. An app can store its data in the folder '/data/data/apkname'. It is possible to clear the data stored by an application by using the Manage Applications feature in Settings | Applications | Manage Applications.
Nand
See Flash Memory.
Nandroid
Nandroid is used to backup or restore backups from Recovery.You can chose to either do a regular backup (Phone only) or a backup + sd-ext (Phone + Apps2sd ext.)Both will backup your whole system, the second will include apps saved on your sdcard's sd-ext.
Radio
The Radio on a Hero is the part of the phone that deals with mobile connections. It handles talking to the GSM/3G network, Bluetooth, WiFi and GPS. The radio contains software that controls how it operates, and newer versions of radio firmware are made available from time to time in [[#RUU]] updates. These updates are transparent to the user, although users who elect to install custom software can update their radio using an update.zip file made available by members of the modding community.
Flashing the radio is potentially risky, and you should NEVER pull the battery out of a phone that is [[#Flash|flashing]] the radio. If you do so, it is possible your phone will be bricked. Nevertheless, it can give improved battery life, signal strength and data performance, so is often done by users moving to later versions of ROMs.
Care should be taken to only flash the correct type of radio to a phone. NEVER attempt to flash a CDMA phone with a GSM radio or vice-versa. It is likely you will brick the phone if you attempt to do so.
ROM
ROM is literally "read-only memory" but it's usage has changed over time. Today ROM can refer to the non-volatile area of a device's flash memory on which read-only data resides or the packed image to be written to that flash area.
Root
Root is the name of the highest level superuser (su) on Unix-like systems such as Android. The root user, and applications run by the root user, have administrative access to protected files and services which makes it dangerous for normal daily use.
A 'rooted' device one which has been hacked to provide privilege escalation from a standard user to superuser. Rooting a device is usually the first step in installing cooked ROMs.
RUU
An RUU is a ROM Upgrade Utility, which is a Windows executable (exe) file that upgrades the software on your phone. Using the USB connection with the phone, the RUU communicates with the phone's SPL, checking the CID of the device to ensure the user is not installing the ROM on a network branded device (since the networks release their own RRUs with customisations and branding). The RUU is capable of flashing almost everything on the phone, including System, Data, Recovery, HBOOT and Boot. As such, an RUU is a good way to return your phone to the way it came out the box if a warranty repair is needed (be aware that using a new RUU could make it difficult, or even prevent you from rooting the phone in future. It is normally better to upgrade using update.zip files to prevent this, as they do not update the HBOOT to prevent Fastboot in future.
S-OFF/S-ON
This refers to an unlocked/locked NAND drive. HTC lock the NAND on some phones to prevent writing to the /system. S-OFF can generally be obtained by an exploit, by flashing an engineering SPL, or by using an XTC Clip.
SPL
The Secondary Program Loader is a piece of bootcode that initiates the startup of the phone, displaying the initial splashscreen for the device, and loading the initial files from ROM.
It checks to see if a button combination is pressed on bootup (such as that to enter Recovery Mode or the bootloader ), and loads the relevant system software. If no special instruction is given by holding keys, the bootloader loads the normal system software by initialising the boot process from the boot partition.
Flashing your SPL is risky, as the process failing will probably result in a broken, or bricked phone, since the SPL is executed very early on in the boot process, and any error here will prevent access to the recovery or bootloader features.
If you do flash the SPL though, it unlocks the Carrier-ID CID from the device, essentially allowing any RUU to be installed to the device, and allows flashing alternative or custom bootscreens.
Stock
The term stock is often used to refer to a file or part of the software which is unmodified or untouched by developers. For example, a stock ROM would be one which was produced by HTC and which had not been modified or rooted by someone. The term is often used when comparing performance of different ROMs, as a way to refer to the phone as it came out the box.
su
su (substitute user) is a Linux command which, when run without a username parameter, gives the user full 'root' permissions. By default, this command binary (ie. Linux equivalent of an executable file) is not included on Android systems, but the process of "rooting" a phone copies this file to the '/system/bin/' directory thereby enabling the command. Since root privileges can be abused by malicious applications it's highly recommended to install an app to grant and manage access to su, similar to UAC on Windows. VillainROM includes the app called "Superuser" for this.
System
The /system directory on your device is where the main operational software for the Android OS is stored. It has a number of sub-direcories of which /system/apps (where application apk's are stored) is probably the only one users would have need to access. The /system folder is read-only by default and needs remounted via 'adb' to allow write access.
Recovery
The recovery partition is a boot-mode for your phone that allows you to wipe your settings from the Data partition of the phone (a hard wipe), or perform an update using an update.zip file on the root of the microSD card. It is common (although not necessary) to flash a patched Recovery image, such as Amon RA's one. This allows you to run Nandroid backup from the device, and flash modifications, such as [[#update.zip]] files to the device, essentially becoming a means to install sotware to the device. Recovery mode is separate from 'normal' mode, and can be entered by holding down home whilst turning the phone on.
update.zip
An update.zip (does not have to actually be called update.zip if you have a patched Recovery image) is a file containing some files which will be copied to the phone's internal memory. Normally, a new system update or ROM is stored in the file, but update.zip files are commonly used to install modifications such as themes or applications that are installed on the System partition to prevent uninstallation.
To flash one of these files, which commonly would contain a custom ROM for your phone, you would boot your phone to a patched recovery image (whether using Fastboot, or the home+power method if you have a patched Recovery image flashed on your phone)
Update.zip files are cryptographically signed, and more information on how to sign your own files can be found online.
WWE
Stands for World Wide English version of the ROM. There can be local versions of ROMs too. For example VR10 is based on the Taiwan version, VR12 on the WWE one. Interestingly, WWE excludes the English (US) locale.
Now we are done with the definitions

HOW TO ROOT YOUR HTC One V PHONE
This guide may also work for rooting the HTC Wind / HTC Desire S (T328w). If you decide to try rooting your Wind / Desire V, make sure you first download the stock HTC RUU (ROM Update Utility) to recover if there are any issues.
Please note that unlocking your phone’s bootloader does involve the possibility of voiding your warranty, so be certain that you are willing to risk that to root your phone. Moreover, you proceed at your own risk. I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble.
You will need much patience and time, and you’ll need to know how to use SDK tools for Android (see below). If you are a total noob, I do not recommend this for your first project! If you try anyway and get confused with terminology, try looking here for answers: Terminology - CyanogenMod Wiki.
Quote:
Before you begin, make sure that your computer can properly recognize the phone:
You will need SDK tools for Android, Java runtime, and HTC Sync installed on your Windows computer. If you run Mac, I can’t help you. I avoid all that narcissistic iStuff like the plague.
1. You only need to install HTC Sync for the drivers that come with it. But the program sometimes causes conflicts, so during this procedure, make sure it is not running. Open Task Manager in Windows and kill it. If you don’t use HTC Sync, you may also open Control Panel and uninstall it without uninstalling the drivers.
2. With the phone on, connect the USB cable. Make sure the phone is connected in Charge only mode.
3. Enable USB debugging by going to Settings > Development > USB debugging.
1. Perform a full backup your phone’s data
Unlocking the bootloader will involve doing a factory reset. This will result in the loss of all accounts, emails, texts and apps installed on the device. However, data on the SD card such as music, photos and videos will be safe. The device will not format the SD card.
2. Update your software version
To update your software after rooting, you will have to go through hassle of re-flashing the stock recovery and re-locking the bootloader. The phone will lose root and you’ll have to go back through steps 3C-5F, so make sure you’ve updated first. To manually check if a software update is available, go to Settings > About > Software updates > Check now.
3. Unlock your bootloader at htcdev.com
The next step is to head over to htcdev.com and follow the procedure there to unlock your bootloader. This is the step that can void your warranty!
3A. Getting started
Create an account at htcdev.com and login. Click the Unlock Bootloader icon and Get Started button. On the next screen, drop down the “Select Your Device” list, choose All Other Supported Models and click the Begin Unlock Bootloader button. Then, fill out the two nasty forms telling HTC that it’s perfectly fine with you to possibly lose your warranty by going through with this process.
3B. Obtaining your unlock token
The first page of instructions shows you how to boot the phone into HBOOT, select FASTBOOT and connect the phone to your computer via USB. But the instructions are not right for the One V since it doesn’t have a removable battery. So here’s the replacement procedure:
Step 1 – No need to shut the phone down.
Step 2 – To enter HBOOT (or “bootloader mode”), the power button for longer than 10 seconds. As soon as the screen turns black, hold down volume and let off the power button. At the top of the screen you will see ***_LOCKED_***.
Step 3 – Use the volume rocker to select FASTBOOT if it’s not selected already. You may have to wait for the device to run through a routine check for zip files to update.
Step 4 – Connect the phone to your computer using the USB cable.
If you followed the directions above regarding SDK tools, Java Runtime and HTC Sync, you can skip page 2 of the instructions (steps 5-7) and move onto page 3.
In Step 8, you open a command prompt in Windows and navigate to the folder where you installed SDK Tools (it should be c:android-sdk-windows or c:Android) and type the command
Code:
fastboot oem get_identifier_token
Step 9 is where most people get hung up. Make sure that you do not select any spaces next to the identifier token, or any lines above or below the Identifier Token Start/End.
Paste the identifier token copied from the command window above into the box at the bottom of htcdev.com’s page 3 in your browser and click the Submit button. You will receive an email from htcdev.com with the subject “The key to unlocking your HTC Device” that has an attached file named “Unlock_code.bin” and a link to continue the unlock process. Download the attachment into the folder you installed Android SDK tools and click on the link to continue from page 4. You may have to log back in.
3C. Unlock the bootloader
For Step 12, go back to the command prompt and make sure you are in the folder where you installed Android SDK tools and downloaded the file “Unlock_code.bin” above. Now you will flash “Unlock_code.bin” to the phone using the following command:
Code:
fastboot flash unlocktoken Unlock_code.bin
You will see the following warning screen on the phone, again confirming that you are willing to waive your warranty rights to unlock the bootloader:
Use the volume rocker to select Yes (up one click) and press the power button once. The bootloader will proceed to erase all your data, unlock itself and reboot the phone.
After running through the setup wizard, go back into HBOOT (turn the phone off with the long press, hold down volume and press the power button) and confirm that you’ve unlocked your bootloader successfully. You should see ***_UNLOCKED_***. Success!
4. Install ClockworkMod Recovery
A custom recovery allows you to backup and restore ROMs including all user apps, data and cache to the SD card. It is also used to flash scripts, custom kernel and custom ROMs, which will come in handy at step 5 below where we root the phone.
1) There are two types of One V - the international GSM version (uses a sim card) and the U.S. Sprint/Virgin Mobile CDMA version (no sim card), and there are custom recoveries for both types that aren't interchangeable.
If your phone uses a sim card, download recovery-clockwork-5.8.4.5-primou.img from ClockworkMod's index of recoveries.
If you have a U.S. Cellular/Sprint/Virgin Mobile (U.S.) device that doesn't require a sim card, download cwmrecovery.img. Be sure to click the thanks button for Android Forums member jmz for his handy work.
As an alternate, PrimoC/CDMA users (no SIM) can download and install jmz's TWRP2 Recovery. See the directions in his thread: [VM/PRIMOC][RECOVERY] TWRP2 Recovery 7-10-2012
2) Reboot the phone into bootloader, select Fastboot and connect the USB cable.
3) Open a command prompt and navigate to the folder where you saved the recovery image in step 1 above. Type the following command:
Code:
fastboot flash recovery recovery-clockwork-5.8.4.5-primou.img
or
Code:
fastboot flash recovery cwmrecovery.img
4) Reboot the phone back into bootloader using the following command:
Code:
fastboot reboot recovery
You should see the new Recovery.
5. Now on to root the phone!
5A. Head over to XDA Developers and download the SuperSU access management tool. You'll want to grab the attached file at the bottom of the OP called CWM-SuperSU-v0.9x.zip. This will root your phone and install the SuperSU app in one smooth motion. Much thanks, credit and kudos go out to XDA user Chainfire. Login over at XDA and hit the thanks button for him somewhere or donate to his Paypal account and buy him a Coke.
5B. Copy CWM-SuperSU-v0.9x.zip to your SD card.
5C. Restart the phone into HBOOT again and select Recovery. After Recovery has launched, choose install zip from sdcard > choose zip from sdcard and select CWM-SuperSU-v0.9x.zip.
5D. Reboot the phone. It is now rooted!
5E. Go to the app drawer and click on SuperSU. Update the binary when prompted. It’s icon looks like this:
5F. Install and open any app requiring root access to confirm that the phone is rooted.
6A. Backup your stock HTC ROM in CWM5 Recovery!! Before you make changes to your stock ROM or decide to install a custom ROM, this is a must! Reverting back to a stock HTC ROM after installing a custom ROM can cause massive headaches. Restoring from a backup is MUCH easier. It will also help if you've ruined your ROM causing a softbrick. You just boot into CWM5 Recovery, do a factory reset and clear cache (including Dalvik) and do a restore from your previously backed-up ROM.
So, reboot the phone into bootloader, use volume down to select Recovery and press power to select. When Recovery comes up, select Backup/Restore > Backup. Then find the backup you just made on the SD card (under sdcard/clockworkmod/backup) and copy that to your computer for safekeeping in case you loose or format your SD card.
6B. Install custom ROMs Now we play the waiting game and wait for overclockable kernel and custom ROMs. I’ll be updating this section as things happen so come back and see what’s new.
The procedure for flashing a custom ROM is as follows:
1) Boot into Recovery and backup your stock ROM if you haven't already. If you don't and something goes wrong, you'll have a major headache on your hands. *DO NOT* skip this step.
2) Download the ROM and copy it to the root directory of your SD card.
3) From Recovery, o a factory reset, wipe the cache partition and wipe dalvik cache (under Advanced).
4) Install the update from the SD card.
5) Reboot the device.

How To Install Custom Roms
1.Boot into recovery
2.Do a nandroid backup
3.wipe
a.cache
b.dalvik cache
c.data
d.system(isnt necessary)
3.Select install zip from sd card
4.select the rom and put yes
And the rom will install
How to install custom kernels
1.Boot into bootloader
2.enter fastboot and plug your phone into your computer
3.open cmd and type cd and navigate to to where you placed the fastboot.exe and boot.img
then type:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
AND the custom kernel would be installed
How to Make a Nandroid Backup
1.boot into recovery
2.enter backup and restore
3.select backup
So it will backup all your rom
How to restore stock rom after installing custom rom
1.Boot into bootloader flash stock kernel(DO THIS ONLY IF YOU HAVE INSTALLED A CUSTOM KERNEL WITH THE ROM)
2.Enter recovery
3.select backup and restore
4.select restore
And stock rom will be installed
How to partition your sd card and make internal storage bigger
Partitioning is the act of dividing into parts and with SD Card it means to divide sd card into different virtual parts. So, you might be asking why we need to divide our sd card into two parts. This need has come into existence with devices such as Samsung Galaxy Pop/Mini GT-S5570, Samsung Galaxy Ace, Galaxy Fit and other smart phones that have relatively low internal storage (only about 180 MB or 250 MB) as a result it has been very difficult to manage our apps and data within the internal storage. So, to remove such low internal memory problem we are going to partition our sd card and then install the Darktremor Apps2SD Script so applications and games will install to this sd-ext partition that we are going to create by default and we won’t have to worry about low internal memory problem.
Before beginning it is assumed that you have a custom clockwork mod recovery and a custom rom is installed on your device. Alternatively, if you are in a stock firmware/rom and want to partition your sd card please Install Clock Work Mod Recovery and Flash a Custom Rom on your device. Also since partitioning your sd card will erase all your data stored in sd card, it is recommended that you backup your data to your computer. Now that you have backed up your data please follow these simple instructions to partition your sd card and install Darktremor App2sd script on your android smart phone.
1. Reboot your device into Clockwork Mod Recovery.
2. Go to Advance>>Partition SD Card option on your recovery and select a size for ext 3 partition. This will create an ext 3 file system partition on your sd card called sd-ext. The size of your sd-ext partition should be determined on the basis of how much apps and games you are going to install on your device. If you are not of type who wants to test every app or a normal user 2 GB of sd-ext partition should be enough. Determine the size that best suites you and proceed.
3. Also, select swap partition size as 0 Mb.
4. [Optional] Format your sd-ext from mounts and storage>>fromat /sd-ext option in CWM recovery.
5. Reboot your device and open a terminal emulator or shell commander and type in the following command to make sure that your second partition (aka sd-ext partition) is mounted at boot.
mount | grep sd-ext
You should see the following code:
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodelalloc,data=ordered)
6. Now download Darktremor Apps2SD and copy it to your sdcard.
7. Reboot your device in CWM recovery and then mount your data and system by going to mounts and storage>>mount /data and mounts and storage>>mount /system options respectively.
8. Now go back to main menu and go to install zip from sd>>choose zip from sdcard option and select the dtapps2sd-2.7.5.3-beta04-signed.zip file you downloaded from above.
9. After the script is installed reboot your device.
That’s all. You have successfully installed Darktremor Apps2SD on your device. Note that the device will reboot again after you reboot your device. This is just to move all your apps to the second partition (sd-ext partition) and is normal. Also if you want to manage your Apps2SD settings you can either use commands in terminal emulator or download this APPS2SDGUI application from market and manage everything from there. One of the useful command can be a2sd help. Try it on any terminal to see the help file that comes with Darktremor A2SD.
Here are some commands that you can run in terminal emulator for configuring a2sd. You can find more info about them as well as other commands by typing a2sd help command.
a2sd check : Checks a2sd status; displays information incl. where your apps, cahce and data are stored.
a2sd cachesd : Moves dalvik cache to sd-ext partition.
a2sd nocache : Moves dalvik cache back to internal storage.
a2sd data2sd : Move /data/data to /sd-ext/data .
a2sd nodata : Move /sd-ext/data back to internal storage.
a2sd remove : Moves apps back to internal storage and sets no a2sd flag.
Now some precautions tips you should take in mind. After installing Darktremor Apps2SD don’t move your apps to sdcard either from Manage Applications Settings or by using app2sd pro or similar applications because it will ruin all your settings and your script will not work. Also you may notice that your used space in internal storage shown in Manage Applications Setting is not decreasing even after you install Apps2SD and you may think that the script is not working. But remember if you followed all the instructions from above and got the same results as explained above then the script is working. It is shown so because system is fooled to believe that the apps are in internal storage but in reality they are stored in the secondary partition we created (i.e. in /sd-ext/app folder) on your device.
How to install recovery
1.grab the recovery file and put it in thre folder where fastboot exists
2.open cmd and type cd and navigate to the folder where they both exist
3.Then type:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache

RESERVED

RESERVED2

RESERVED3

RESERVED4

RESERVED5

RESERVED6

Maybe if you used the search function on the site,before you posted this,you would'nt be the author,fan and publisher of your own thread...... http://forum.xda-developers.com/showthread.php?t=1466228

[ROOT + CWM 6.0.1.5 or 5.5.0.4] Lenovo IdeaPad A2107A (-H)

The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
------------------------------------------------- UPDATE 3 ---------------------------------------------------------
I think there is even easier way than the one I originally posted above.
BUT I cannot be sure that it will work with all of you - the reason is that I made so many changes to my A2107A-H that I do not know whether this method works "just because it's universal" or because my tablet was tweaked far enough.
On the other hand when you consider it reasonably it looks like it's quite simple and there is no particular reason why it shouldn't work with a stock A2107A.
So...
What you need:
1 - this package: http://www.mediafire.com/download.php?fbuzi5xjofs7vgf
2 - PC running Windows 7 would be the best (7 gave me no problems at all - takes 1 minute to do it). I made it on Windows 8 as well but there is a lot more fuss to install the proper driver.
What you do:
1 - turn on USB Debugging on your tablet
2 - connect the tablet to your PC (if it's the 1st, some default drivers will install - that's ok)
3 - tap on the notifications area in the "Connect as" change to "MTP" - this is quite important !
4 - from the downloaded package run the "Flash_tool.exe"
- click "Scatter-loading" on the right and find "MT6575_Android_scatter_emmc.txt"
- in the list in the lower part of the window you MUST have the "PRELOADER" (super important) and "RECOVERY" ticked and leading to the correct files. The PRELOADER = "preloader_lenovo75_a2_ics.bin" (in the package) and the RECOVERY is the recovery file of your choice -> there are 3 in the package - pick the one you want. You can flash them over and over so if you don't like one then try the other.
5 - click "Download" above - you will see a prompt saying that not all images were loaded - that is fine - we only want to flash the RECOVERY - so click "Yes"
6 - now the Flash tool is waiting for the tablet - press "reset" on the back - Windows will recognize a new device (and WILL NOT find the driver unless you have done it before) - no worries, you have the correct driver.
7 - open Windows "Device manager" and locate the MT65..... unrecognised device -> update / install driver -> point Windows to "USB VCOM Driver" folder from the package and pick your system. My Windows 7 found the driver on the spot but asked to confirm the install - "insecure" driver - I obviously clicked "install anyway" and so should you.
8 - once the driver is loaded the Flash tool will flash the new recovery file - you will see some colour progress bars in the program - at the end you should see a green circle.
That is it. Unplug the tablet, press reset on the back and you can now enter the recovery mode.
FUN FACT: the "reset" button on the back is not really a reset button, it's more like physical cut off button to temporarily disconnect the battery.

I have the Lenovo A2107A under Vodafone's brand Vodafone Smart Tab II 7
It has Android version 4.0.4 and compilation: A2107A_A404_010_002_120913_VODA
Imanaged to root it and install CWM using this thread. But somehow I was not able to create the CWM modded recovery.img
I used the one provided here and it worked fine.
Thanks for this.

I can't connect tablet to PC
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for you actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Window device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
Click to expand...
Click to collapse
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.

optical99 said:
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
Click to expand...
Click to collapse
Hi there,
Try those drivers: http://www.mediafire.com/?vx2hyv7dpwlmeyy
They come from the current Android SDK but I am running a 64 bit system and I'm not sure if those drivers will work with 32 bit systems.
Fingers crossed!

I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.

optical99 said:
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
Click to expand...
Click to collapse
I had to use the PDANET from this link.
http://forum.xda-developers.com/showthread.php?t=1982334&page=6
Should be the first post.
Sent from my Samsung Galaxy Note running JellyBeer using Xparent ICS Blue Tapatalk 2

First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance

makbro said:
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
Click to expand...
Click to collapse
I'm glad you find my post useful.
As for the calling feature - it's not actually working
You see, to have the calling app (in other words "the phone" app) in the app drawer all you need to do is change one tiny value in framework-res.apk.
This value is telling the system weather the whole device is supposed to handle voice calls or not. I just tricked the system to make the Phone.apk visible but there is a lot more do be done in order to make a real call over the cellular network.
I've just had this tablet for a week and I didn't have much time to dig into this topic. Let's see what the weekend brings
Be patient, I think it's just a matter of time when someone posts a user friendly guide... Or search yourself and share what you find with the community.
Take care.

works fine
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job

optical99 said:
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
Click to expand...
Click to collapse
Glad I could help by showing the link. Glad you got everything else taken care of.

This is an awesome post! Thak you very much.

Need help at step 4
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
Click to expand...
Click to collapse
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance

makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
Well, this happened to me once and I think the reason was that the path was too long - I guess it may have something to do with the fact that the .bat is a simple "program" and can have some problems with handling long paths.. specially with "national" character in them.
Try finding a location as close to the root of the drive as possible, and make sure you have full R/W access. Or try with a pendrive for example.
Since you made a backup of your ROM I think you are quite safe with using the recovery I uploaded - first post -> UPDATE 1.
They seem to fit all 2107A devices. If not I will tell you how to restore the original recovery from your backup.
You can also read UPDATE 3 I just made - your choice.

Thanx
Hello csns,
Thanx to your help, I have also got CWM recovery working on my device.
BTW I saw these two posts on a forum in Russian (I guess)...I used google translate and am pretty sure these two posts that I provide links for below have two modified ROMs with everything working, including phone and radio !!! The only draw back is that once you flash these ROMs you'll get Russian language, which can be changed to English from the language menu
I plan to fo it myself as well tomorrow,would let you know the outcome
http://4pda.ru/forum/index.php?showtopic=286687&st=920 (go down to the post labelled "A2107_Foxtrot_v100")
and
http://4pda.ru/forum/index.php?showtopic=286687&st=440 (go down to the post labelled "Прошивка Tasemart
MOD 1.1")
and of course you can also try the "Angeleas_Final" modified ROM also that I'll upload and provide links to tomorrow
Thanx again for all your help !!!

I also had many trouble getting the cwm bat file to work. It is very picky about its path and arguments on Win7.
I moved the michfood folder to C: and moved my own recovery.img to C:\michfood\recovery.old
cd C:\michfood
cwmr\ 6015.bat recovery.old
That worked - otherwise it wouldnt finish the cpio stuff.
Reworking that horrible script to work on linux would have probably taken less time -_-
Anyway - thanks!

Permissions problems on Windows7
Hi,
I Had the same problem.
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
Click to expand...
Click to collapse
My solution:
It was required to use a directory not to deep in folder structures, so the best is as short as possible like "C:\michfood".
I had to add "Full Control" permissions for "everyone" to the "michfood"-directory and enable the "replicate permissions to subfolders"-option (I don't know the exact designation because I use it in german ... )
I had to delete an existing "Recovery" folder inside the "michfood"-directory from earlier attempts to create the new file and for this I had to take over the ownership of the "Recovery" folder before I was able to delete it.
The original Recovery.img must be in a different folder than "michfood". This can be on the desktop but for a shorter path it could be in the root directory.
I had success after copying "cwmr 6015.bat" to "go.bat" (it's shorter and does not contain any space in it) and calling it from command line from its directory( C:\>cd C:\michfood ) with: "go C:\Recovery.img" ( I had Recovery.img on C:\ ).
makbro said:
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
I hope this helps ...

Thanx
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem

makbro said:
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
Click to expand...
Click to collapse
HOW?
Tell me what you did...

Cristian.Ene said:
HOW?
Tell me what you did...
Click to expand...
Click to collapse
I copied the folder as "C:\michfoods" and recovery image file as "C:\recovery.img" and gave the command "cwmr6015 C:\recovery.img"...Before that, I removed the space from the file name "cwmr 6015.bat" and saved it as "cwmr6015.bat".

Hi, i rooted succesfuly my a2107a device and installed backup Gscript ...loading "back_mt6575_a4_v2c.sh and saving it , but when it comes to run...nothing...only the counter saying how many sec's till stop.Any ideeas why?

[GUIDE] Rooting and CWM on PORTRONICS LIMEBOX!!!!

For all you Indian Users, or anybody who owns a Portronics Limebox running GB; root and CWM has finally been achieved!
Disclaimer: I am not responsible if you end up bricking your device. This procedure has been known to work for my Limebox. Deviate from the procedure and you have no right to blame me....
After lots of hours of extensive searching (with absolutely no help from portronics), I found an exact match to our device: G-Box (See the Remote???). Our Device is a Rockchip Processor, specifically RK2918. Rockchip processors are known to lock down the /system partition with a filesystem called cramfs. Don't worry, that can be solved too!
Before we start, Understand the 3 modes you can set the device in:
1. Normal Power On (Self-Explanatory)
2. Recovery Mode (Stick a Pin in the Reset Hole and keep the Power Button pressed at the same time)
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?

unable to detect limebox on my win7 64bit laptop
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?[/QUOTE]

My apologies for the very late reply. As I recall, the drivers are for 32bit, have you repeated the steps on a 32bit machine? Did the pc attempt to recognize it?
huzefaid said:
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?
Click to expand...
Click to collapse

tried on 32bit machine, the pc did'nt recognize it
please help
do i need to connect monitor with hdmi port to view flash mode.?
i have press reset pin and also powered on the device at same time, but my pc did'nt recognize it.i have also started rk29androidtool to check it it detects the device but no luck.

[root] Wiko Fever [MT6753]

(Rooting guide at post #5 http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5)
(Stock ROMS at post #7 http://forum.xda-developers.com/showpost.php?p=63939728&postcount=7)
Hi,
The new flagship from Wiko, the Wiko Fever, it's a great device. :good:
Here my research with it:
- MT6753 with 16GB ROM and 3G RAM
- Bootloader LOCKED (you can unlock it using one option in the developers hidden menu (you know how to enable it!) and then after reboot in the bootloader execute "fastboot oem unlock" (note, that selecting OK you will erase your data!).
:good:
- You can download an EXPERIMENTAL (=ALPHA) custom Recovery (CWM-Carliv) from here (you need to flash it to use it):
***removed***
- Also you can download the original DUMP of the boot.img and recovery.img from here:
http://www.sendspace.com/file/zy9q6g
:silly:
You can pack/unpack the recovery/boot using the CarlivImageKitchen selecting "normal" (not MTK) version!

..

Hi,
This device (Wiko Fever) is the same as Micromax Canvas 5 E481:
http://www.micromaxinfo.com/mobiles/smartphones/canvas/canvas-5-e481
Also, is identical to Blue Life ONE X:
http://www.bluproducts.com/index.php/life-one-x-2016
Follow the thread (with custom Kernels) at:
http://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428
Then the same firmware and rooting procedure will be shareable between both!
Here a great guide for Wiko Fever & Clones:
http://forum.xda-developers.com/android/general/guide-clones-t3421539

Hi,
Here the scatter file for Wiko Fever Lollipop 5.1.
Two versions: a) extracted from stock update (scatter_stok); b) made by hand (scatter3).

Rooting GUIDE
Hi,
Good news: Rooting is done! :victory:
Here is the guide for rooting your Wiko Fever:
Warning (for newbies): First copy all indicated files to your SD card using your phone in normal state. Or use a PC and a SD reader for copy them when indicated.
1) Unlock bootloader:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Install custom Recovery:
2.1) Download from here the BETA 1 of CWM BETA 2 of CWM BETA 3 of CWM: http://www.sendspace.com/file/4g87bj
OR Download TWRP Beta 1 for Lollipop 5.1 from Hanuma: http://www.sendspace.com/file/y4jel8
(Original post: http://forum.xda-developers.com/showpost.php?p=64543542&postcount=45)
OR Download TWRP 3.0.2.0 for Marshmallow from Hanuma: https://www.sendspace.com/file/9ms9zz
(Original post: http://forum.xda-developers.com/showpost.php?p=67531723&postcount=217)
2.2) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Then execute command “fastboot flash recovery recovery-custom-wiko-fever.img”; and then “fastboot reboot”.
3) Rooting:
3.1) Copy last beta of SuperSU v2.52 to your SD Card (file BETA-SuperSU-v2.52.zip).
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3.2) Boot in the CWM with “Vol+” and “Power” buttons.
3.3) Install ZIP from external-sd card.
3.4) Reboot and don’t select “fix root”, only “Yes”.
3.5) After boot, start SuperSU and configure it. Root done!
4) Xposed install:
4.1) Copy last release of Xposed Installer to your SD Card. Use files from here:
http://forum.xda-developers.com/showthread.php?t=3034811
* xposed-v78-sdk22-arm64.zip
* XposedInstaller_3.0_alpha4.apk
* xposed-uninstaller-20150831-arm64.zip (in case of errors).
4.2) Boot in the Recovery, and install the framework (file xposed-v78-sdk22-arm64.zip).
4.3) After reboot, install the Xposed APK (file XposedInstaller_3.0_alpha4.apk).
4.4) Reboot. The Xposed framework is running.
Enjoy!
Notes: Before starting to root your device I recommend to do a full DUMP of the firmware using the SP Flash Tool. Use my handmade scatter file. :angel:
Thank you to all developers & supporters! :highfive:

ChangeLog:
- Beta 3: Fixed ADB shell with root uid.
- Beta 2: Fixed SELinux context support in ext4 filesystem. Full woking for rooting!
Note: If you like to use adb shell in recovery but an error like "exec '/system/bin/sh' failed: No such file or directory" then first mount /system partition.
- Beta 1: Don't use this version, has a bug with SELinux contexts!
- Alpha(1,2,3): Pre-releases.

List of stock ROMs (for flashing with SPFlashTools) for Fever V8 (16GB/3GB) only:
- Lollipop v39 (last version until 5/2016): http://world.wikomobile.com/scripts/telecharger.php?id=140&type=MAJ
- Lollipop v22 (update 02.12.2015): http://fr.wikomobile.com/scripts/telecharger.php?id=105&type=MAJ
- Lollipop v18 (update 10.11.2015): http://fr.wikomobile.com/update-918-FEVER-4G
In case you need it!
List of stock OTA ROMs (for flashing with CWM/TWRP Custom Recovery):
If you have rooted your device, you can upgrade using these ROMs...
- Lollipop v39 (pre-rooted, with Xposed and ViPER Audio):
part 1: http://www.sendspace.com/file/d0js30 md5: e8706e0f5860e907fb8169856fc5e3b9
part 2: https://www.sendspace.com/file/iv4mnb md5: dd76926221ef40c872e4548a9b9e1f19
part 3: https://www.sendspace.com/file/6lfd18 md5: 838e6e608983a296611a284831fffd47
WARNING: At time this is untested! Give feedback with a post in the thread!
Decompress it using 7zip in your PC, copy files to your SD Card TWRP/Backup folder, and restore this backup with TWRP
Probably you want to use these versions!

Hi,
God news! I de-bricked my device... ****ing erroneous selinux context attributes in /system/lib64/ and /system/bin/ are the reason!
So, I don't futher need the stock SYSTEM partition. I'll continue with the rooting process... soon I'll publish it.

this device can support cm12-cm13?

djsolidsnake86 said:
this device can support cm12-cm13?
Click to expand...
Click to collapse
I hope!
Maybe will be easy for some developer to port one CM13 firmware for MT6753 to this device.
The opensource package for this device isn't at time available. Sorry!

Verify that the bootloader is unlocked
Hi manos78, first of all thanks for this guide and all the efforts you are putting into this.
manos78 said:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode. Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
Click to expand...
Click to collapse
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Thanks again!

hi guys, i followed the guide and all worked also with the last update

cippaciong said:
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Click to expand...
Click to collapse
After the command "fastboot oem unlock" If you see the Warning message and the device is rebooted and formating the data partition, then you have for sure unlocked the bootloader.
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.

Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/

manos78 said:
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Click to expand...
Click to collapse
Unlocked
You have been really helpful, thank you!

oile said:
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
Click to expand...
Click to collapse
Hi,
I try to boot the custom recovery image with fastboot without flash and it fails. So for rooting, at time, the only way is: unlock->flash custom recovery->install superSU. But after that, you can try to: flash stock recovery->re-lock, if you like (not tested by me! Be carefull!). However, with the custom recovery you can do full backups, so I recomend it. The side effect is that you can't upgrade with OTAs.
Another option is use the original stock firmware and readback/flash the SYSTEM partition and modify it using an external computer (modify the IMG). But, this solution is quite complex.
Finally, related to the SD-CARD. The "internal memory" is only for "media", not for Apps. I use one 64GB SD on my Fever and I store in it: photos, music & ISO/IMG images. Any other data is in the internal storage (emulated sdcard). Also, I "installed" (=moved) some huge games (>100MB) to the sdcard (the real SD); and I store my Google Kiosk and Music files on the sdcard (also the real SD). Please, don't care about the sd storage, is working right on the stock firmware.
:good:

Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)

oile said:
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
Click to expand...
Click to collapse
In stock Fever ROM:
/sdcard --> the REAL SD Card (the Sygic data, Google Music & Kiosk, etc. are in the REAL SD Card)
/storage/sdcard1 --> the EMULATED SD (internal memory)
Then you can use the SD as real one with Apps, and use alternative (emulated) when you like. The "media" Apps can use sdcard0 (real) or sdcard1 (emulated).
Related to this sentence: "hese apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)"
Please, remember: both, external memory and internal memory, have LIMITED life (write operations). Then, what you prefer: write more on the internal and not interchangable memory, or in a removable and inexpensive memory?
Please, think well! :angel:
Also, FYI, in my current Wiko Fever I use a 64GB SDXC UHS-II, far away than a simple class 10 (x15 reads/x30 writes).

oile said:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
Click to expand...
Click to collapse
I'm quite accustomed to filesystems and partitions since I've been using Linux for many years but I've got almost zero experience with Android internals, so please help me to understand if I got this right.
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
I'm sorry if my questions might sound dumb to you but I'd like to start tinkering with Android a bit more but having a hard time finding a good starting point.

cippaciong said:
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
Click to expand...
Click to collapse
Hi,
Unlock bootloader is for booting NON-SIGNED kernels (the boot or the recovery), not for partitions.
When you unlock the bootloader you can install (or boot) a CUSTOM recovery. In the custom recovery you can mount and modify the SYSTEM partition (where is included the root).
For "flash" or "dump" the internal memory of the device, if it's using a MTK cpu (like the Fever) then you can use SP FLASH TOOL. You have the scatter file in this thread!

Database Info

welcome