Related
A friend of mine gave me his x10i phone to play, so i decided to follow all the proper steps to get the device rooted and install 2.3.4 on it.
I have downloaded the flashtool v 0.5.3.0, but it does not detect the device. I have also installed the drivers on the system from flashtool\drivers folder
When I click Check Drivers, i get the following output:
12/041/2011 16:41:47 - INFO - List of connected devices (Device Id) :
12/041/2011 16:41:47 - INFO - - USB\VID_0FCE&PID_612E\CB511ND245: OK
12/041/2011 16:41:47 - INFO - List of ADB devices :
12/041/2011 16:41:47 - INFO - List of fastboot devices :
Another problem I have is that Debug mode is on, but the flashtool always says it is off. I tried all i could including upgrading the stock rom from sonyericsson site, but at this stage, I am ready to give up. I do not see anyone else is experiencing this problem.
Any advice is appreciated.
screw the drivers in that folder
install the legit ones from the SE webstie
install the PC Companion and it will do everything for you
then try. If does not work message me or reply here
tried it all from scratch at home on windows 7 (first attempt was at work on XP).
At home everything worked fine Thanks!
do you want Unlocking you bootloader?
try my way, its stands in my signature.
I think i was able to unlock it. In fact, sorry, I do not know what "unlocking bootloader" is, but what makes me think that I've done it is that i was able to flash Doom kernel with wifi and one of the custom ROMs on it. Also I got root access on the phone. Recovery console (CWM ?) is working too.
Correct me if i am wrong, but this is as far as i can go with this device and nothing else needed to crack/install etc.
One issue i noticed is that GPS does not work and settings are just not there, but i guess it is a ROM/kernel related question which i will explore further.
unlock bootloader
makes it a lot easier and nicer when you install a custom rom
um
use flashtool
under plugins category
Tutorial includes stock firmware .ftf files for Flashtool!
Changelog:
31/05/2012 - Adding firmwares.
13/06/2012 - ICS update.
14/06/2012 - Adding posts to keep improving. Massive dictionary update!
17/07/2012 - Few firmwares added!
16/08/2012 - Scrolling made easy!
07/06/2013 - Time to do something good!
This tutorial has been created to help XDA members in order to modify their 2011 Xperia phone. This tutorial is originally made for Xperia Ray by hansip87, link to original topic forum.xda-developers.com/showthread.php?t=1426912. Topic has been modified to fit the following phones:
Xperia Active (ST17)
Xperia Mini (ST15)
Xperia Mini Pro (SK17)
Xperia Live with Walkman (WT19)
These tutorials can also work on other 2011 Xperia phones. Instructions will also work with ICS unless written otherwise, so read carefully!
All kinds of ideas/comments/critism are always welcome.
Everything you do is on your own responsibility. I am not responsible for any damage that you have made to your phone.
Tutorial includes:
Android Dictionary
Root the Phone(GB and ICS)
What to do after rooting(apps etc)
Installing stock firmware and downgrading
Install Busybox and CWM Recovery
Unbricking your phone(after OTA update)
Install Supercharger to optimize Memory and KAK to optimize Kernel
Edit build.prop for additional optimizations
Enable Dual Band and Burst Mode for Wifi
Unlocking bootloader
Installing custom kernel
Installing custom ROM
Relocking bootloader
Preparing for ICS
Overclock/Underclock/Undervolting guide
Optimizing battery life
Downloads
Frequently Asked Questions(FAQ)
Yet to be added:
List of system apps and which can be removed
Depending on what tutorial you will follow, you may need:
Stock ROM on your Xperia and USB cable
PC Companion installed on your computer (for base drivers)
Flashtool(Flashtool topic and download)
Enable "USB DEBUGGING" from Menu -> Settings -> Applications -> Development
Enable "UNKNOWN SOURCES" from Menu -> Settings -> Applications
Set Connectivity mode to MSC from Menu -> Settings -> Sony Ericsson -> Connectivity -> USB Connection Mode
Root Explorer or any file manager that provides access to root (I personally use ES File Explorer)
1. Android Dictionary
ADB - Short for Android Debug Bridge. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
Android - Operating System for smartphones and tablets, based on Linux, built by Google, similar to Windows on PC.
AOSP - Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK - An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Baseband - System of a smartphone, that controls the cellular radio systems(GSM, 3G, HSDPA etc).
Bootloader - Controls the booting process, makes sure that you will access User Interface. These programs tell the Android device how to start up, and are critical to its functionality.
Build.prop - A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations.
BusyBox - Command line bridge, used to give commands to Android system. You will need app to send commands, it will use BusyBox to send the commands.
Brick - A phone, that you paid a lot for and now you can use it as brick, because it doesn't start up.
CWM/ClockworkMod Recovery - A specific program, that is used before booting to Android. Allows the user to make full backup of system and install custom ROMs, updates etc.
CM - Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
Dalvik Cache - The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
Deodexed - Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
Downgrade - A job, that you have to do, when you want to get from newer firmware to older firmware.
Factory Reset - This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card.
Fastboot - Command Line Tool to edit Android filesystem. Unlike flashmode, this allows flashing unsigned partition images.
FC - Short for FORCE CLOSE. See FORCE CLOSE.
Flashing - The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
Flashmode - Phone mode, where you can freely flash any firmware to your phone via WotanServer or Flashtool.
Force Close - When a program on the Android device becomes unstable, the DALVIK program will force it to terminate to prevent further system instability.
GB/Gingerbread - Android 2.3 version, codename Gingerbread, mostly used shortly as GB.
Governor - A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA - Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS/Ice Cream Sandwich - Android 4.0 version, codename Ice Cream Sandwich, mostly used shortly as ICS.
Kernel - Bridge between hardware and Android, used for hardware information exchange and control hardware parts(CPU etc).
Launcher - A program that launches programs in Android. Examples are Touchwiz (Samsung), Launcher Pro, ADW Launcher, and Go Launcher.
MD5 Checksum - A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
Nandroid Backup - A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
OTA/Over The Air - Updating your phone firmware directly from your phone via 3G or WiFi connection.
Overclocking - Setting the processor's clock speed to run faster than its default setting, i.e. 1200 MHz (1.2 GHz) vs 1000 MHz (1.0 GHz).
RAM - Random Access Memory, data storage area, where are currently in use apps and services. It is used, because it has really high data transfer rate compared to other possibilities(SDcard, hard disks etc).
ROM - Read Only Memory, data storage, where the data can only be read by system itself. It includes all data to start the Android. Many developers edit this ROM to change Android interface.
Root(ing) - Process, during which user gets access to Android system partition and files, giving the possibility to edit Android.
SEUS - Sony Ericsson Update Service, can be used in some cases to get back to newest stock firmware.
Undervolting - Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
WotanServer - A paid application, which can be used to flash any stock firmware version with kernel to your phone.
2a. Root your phone - Gingerbread
Currently ZergRush method by DoomLord is the simplest way to do it.
NOTE: If you have newer firmware(4.0.2.A.0.62 or 4.0.2.A.0.69), check tutorial point 4 first to downgrade your firmware. This rooting method will not work on those firmwares.
Download the attached file from here, extract it to a folder using any .zip manager, for example 7-Zip.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser app and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2b. Root your phone – ICS 4.1.A.0.562 ONLY
NOTE: Make sure you have Android 4.0.3 and 4.1.A.0.562 firmware! This might not work on Android 4.0.4!
Download the file from this post, extract it to a folder using any .zip manager, for example 7-Zip/WinRar.
Make sure all drivers are installed.
Make sure USB debugging(Menu\Settings\Developer Options\Development) and Unknown Sources(Menu\Settings\Security) is allowed in the settings.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser and Busybox and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2c. Root your phone – ICS 4.1.B.0.431 and newer
NOTE: You need to have rooted version of older firmware(GB 2.3.4 for example)!
Download the Xperia-ROOT.revX.zip file from this post, extract it to a folder using any .zip manager, for example 7-Zip/WinRar.
Make sure USB debugging(Menu\Settings\Developer Options\Development) is allowed in the settings.
Connect Phone to USB.
Execute "01-local-prop.cmd" to create /data/local.prop (this enables android emulator the backdoor).
Follow the instructions in the window.
Update to 4.0.4 via PC Companion/Update Service(DO NOT REPAIR) or Flashtool(DO NOT WIPE DATA!). Else the hack will be lost and root cannot be done.
Open the "02-push-root-files.cmd" file from the folder, it will install Superuser and Busybox and push all required files to system.
Done.
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
3. What to do after rooting?
Congratulations! You've rooted your Android phone. But...what now? Here is a list of what you can do:
Install Titanium Backup. It allows you to backup all system and user apps with all data that belongs to the app. Very useful when installing firmwares and wipe is required. Using this program, you can easily backup and restore lots of apps at once. Also includes some other functions, link to Play Store.
Edit your Android. In this tutorial are some modifications that can be done. Read the forum, explore different sections and look for more modifications(there are thousands of them!), that you can do. Watch out, make sure that it will work on your phone, else you might mess up something and need to reinstall the ROM.
Remove unneeded system apps to free up some space on the ROM. This [/B]topic, http://forum.xda-developers.com/showthread.php?t=1089470, includes info about APKs, that can be removed and what must stay.
4. Installing stock firmware and downgrading
In the newer firmware, the ZergRush exploit has been blocked. If you want to return to stock ROM or you want to get your phone rooted, you have to install (older) firmware to your phone, which can be done 2 ways:
Flashtool, you need to find correct files yourself.
WotanServer, you have to register a account. - Costs €1.99
Flashtool method
Download the correct firmware file for your phone at the bottom of the post.
Make sure Flashtool is installed.
Place downloaded firmware file(.ftf format) in Flashtool\firmwares(by default C:\Program Files\Flashtool) folder.
Start Flashtool.
Click the lightning button and choose Flashmode.
Firmware should appear there, if you have it in correct folder. Choose it.
Turn off your phone, connect USB cable to computer, then press Volume Down button and connect USB cable to your phone.
Flashtool should detect your phone and starts flashing. Follow the instructions.
When it says „Flashing completed“, unplug your phone and turn it on.
WotanServer method
Go to WotanServer.com, make an account and download the client.
Start the client.
It wants to find your phone. Turn off your phone, then connect USB cable to computer, press Volume Down button and connect USB cable to your phone.
WotanClient detects your phone automatically.
Click Advanced Settings and choose firmware (4.0.2.A.0.58 or older if you want to root).
For region, it isn’t a big deal, which one you choose, although picking own one is easier.
Next, enter your account details(e-mail address and password) and click Update. Make sure you have enough credit.
Click Next and it will download proper firmware files and automatically install them.
When it’s ready, unplug your phone and turn it on.
After that you can proceed with rooting your phone, which is explained in previous guide. Or just enjoy your recently installed stock ROM
5a. Installing ClockworkMod Recovery
NOTE: You must have stock and rooted phone!
NOTE: Most custom kernels already include Recovery.
What you need to do:
Go to this link: http://forum.xda-developers.com/showthread.php?t=1346190 and download SE Tweak Installer.
Connect your phone via USB cable.
Start SE Tweak Installer.
Pick CWM, which is for your phone.
Click Install and wait. When it is ready, CWM is installed.
There is one more solution to install Recovery.
Go to Android Market/Play Store.
Search for Xperia CWM Auto-Installer.
Download the app to your phone and start it.
Follow the instructions to install the Recovery.
And enjoy having a recovery.
To enter the Recovery, turn off your phone, then turn it again, when Sony Ericsson logo appears, get ready. When screen gets brighter during Sony Ericsson logo, click Volume down button(I usually keep clicking it until I get into the recovery).
To move around in Recovery, use volume buttons to go up/down, Menu button to enter, Power button for back(in some cases, also back button works).
5b. Installing BusyBox
NOTE: Requires root.
NOTE: If you used zergRush method to root, BusyBox is automatically installed already and you can skip this.
Go into Play Store(Android Market) and search for BusyBox Installer.
Download it and start it.
Follow the instructions and install will be successful.
6. Turning the "brick" into a smartphone
If you had unlocked bootloader and did OTA(Over the Air) update, then you probably ended up with a dead phone, aka brick. Don't worry, it is not completely bricked, still can be saved!
Download UnbrickingXperia2011.zip file from this post below.
Unpack the .zip file and place the .ftf file in Flashtool\firmwares folder.
Open Flashtool.
Get your phone to flashmode, make sure it is turned off, press down Volume DOWN button and connect USB cable.
In Flashtool, click the lightning button, pick Flashmode and choose the Xperia_2011_FreeXperia_ALL.ftf file.
Let Flashtool finish.
Install stock firmware and kernel to your phone.
Remove USB cable from your phone and start your phone.
Try not to brick it again, less problems for you.
7a. Installing V6 Supercharger
Both can be used to improve the speed of your phone. Supercharger is meant to improve RAM, KAK is for kernel.
Install Script Manager.
Download Supercharger from this topic, http://forum.xda-developers.com/showthread.php?t=991276, make sure to download the "V6_Supercharger_for_Android-update8.sh.txt" file.
Place the file on root of your SDcard, that is the main folder on SDcard(where everything else is).
Open Script Manager, start the V6 Supercharger as normal. You can choose 0 as scrolling speed.
Pick the choice, that you like. I have used Agressive 1 personally(enter the number infront).
When done setup, just exit from the menu (no.17). The result file named 99Supercharger will be generated at /data/ (or in /system/etc/init.d/99Supercharger if you have init.d mod)
(If you use init.d mod, skip this) Open Script Manager, select the /data/99Supercharger.sh, and when the properties window pops up, tag it as "su" and "boot") The ScriptManager will load it at startup and as root, otherwise it will fail.
To test if the script is loaded or not, launch again the setup script(repeat step 4-5) You will find a text like "Launcher is.. xxxxxxx" if it is written as "weak", the script is not running yet. If it is "hard to kill" it is running correctly.
7b. Installing Kickass Kernelizer
This should improve your kernel, haven't tested myself yet.
Go to http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 and download the file.
Open it with Script Manager.
Follow the instructions, I/O tweak is optional, I don't recommend it at this time. Pass when asked.
Press I for Install.
(If you use init.d mod, skip this) Open ScriptManager, select the /data/98KickAssKernel.sh, when the properties window pops up, tag it as "su" and "boot") The Script Manager will load it at startup and as root, otherwise it will not work properly.
Reboot your phone.
To verify, run it again after reboot and when it offers Verify, choose it.
8. Editing build.prop to optimize your phone's system
Build.prop consists of quite a lot lines, which set up, how some phone functions work. To edit the file, you need root rights and a program to explore root(ES File Explorer, Root Explorer etc).
Making a NANDroid backup in Recovery first is a good idea, because if you make a mistake in build.prop file, and phone does not boot into Android, you can still restore it.
Start your Explorer app and go to directory \system
Open build.prop file with a text editor.
Go with your PC to this post: http://forum.xda-developers.com/showpost.php?p=16833651&postcount=1. There are also other tweaks, you can try if you want(you might need init.d script for your ROM for init.d tweaks).
Read the first part of the post, there are some build.prop tweaks, choose which ones you want.
Make modifications in your build.prop file, save it and restart your phone.
Changes should take effect, if you have made a mistake, edit the file again or restore the backup, depending on the situation.
Some more tweaks for build.prop, init.d etc:
http://forum.xda-developers.com/showthread.php?t=1289539
http://forum.xda-developers.com/showthread.php?t=1342241
9. Enabling WiFi Dual Band and Burst Mode
As the title already, this is to increase the internet speed for WiFi on your phone.
Personally, I didn't notice any difference in battery usage.
Open Root Explorer, go to \system\etc and open file named tiwlan.ini with Text Editor.
Edit these lines:
Code:
HT_Enable=0
BurstModeEnable = 0
WiFiAdhoc = 0
to
Code:
HT_Enable=1
BurstModeEnable = 1
WiFiAdhoc = 1
and
Code:
Single_Dual_Band_Solution = 0
to
Code:
Single_Dual_Band_Solution = 1
Reboot your phone.
Tutorials | Firmware | FAQ | First Aid - Updated 13/6/2012
10. Unlocking bootloader
Unlocked bootloader is needed for most custom ROMs and for ALL custom kernels. It allows the booting system to be changed.
This can be done via official way or via test point method. Official way also removes DRM keys, which cannot be restored at all.
WARNING: You will lose warranty with this!
THE OFFICIAL METHOD - You lose DRM!
Go to http://unlockbootloader.sonymobile.com.
Enter service menu, open keypad and enter *#*#7378423#*#*.
Service Info - Configuration, Bootloader Unlock Allowed: Yes/No. If it says Yes, continue. If it says No, do not continue, because it will not work.
On the website, click "Start Unlocking the bootloader".
In the text, there are instructions, what you need to do. Also there are drivers that are needed for this process. Follow the instructions.
Install the drivers, then click Continue.
Enter your IMEI, name and e-mail. Leave out the last number from the IMEI.
You get a code, leave the website open, you will need this code.
Turn off your phone, then connect USB cable to your PC, hold down Volume UP button and connect USB cable to your phone. Blue LED should light up.
You will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
Open command prompt, first enter this
Code:
cd C:\...\android-sdk\platform-tools
Replace C with the correct drive letter and ... with the path to the android-sdk folder. Next, enter this command
Code:
fastboot.exe -i 0x0fce oem unlock 0xKEY
Replace KEY with the key that you got from the website.
Bootloader is now unlocked.
THE TEST POINT METHOD
Go to this topic http://forum.xda-developers.com/showthread.php?t=1285285.
Follow the instructions to patch bootloader.
11. Installing custom kernel
Most custom ROMs will require a custom kernel, some of these include it already(CM, MIUI etc), other you need to find yourself(Hybrom). Installation is done via fastboot. First, you need to find a custom kernel, that will work on your phone. You can find these from Development section.
Make sure your bootloader is unlocked, enter service menu(*#*#7378423#*#*), Service Info, Configuration, if it says Bootloader unlocked: Yes, then it is unlocked.
Make sure fastboot drivers are installed. These should come with Android SDK.
Download the kernel you want. You will need a .img file, which is mostly inside a .zip file.
From the downloads section, download kernel installation package and extract the folder.
Place the .img file inside the folder. If it's name isn't boot.img yet, rename it to boot.img.
Place your phone in fastboot. Turn it off, connect USB cable to your computer, hold Volume UP button and then connect USB cable to your phone. Blue LED should light UP.
Double-click on the flash.cmd file. It will start fastboot automatically and install the kernel.
When finished, disconnect the cable and turn on your phone.
12. Installing custom ROM
Requirements: Unlocked bootloader, ROM .zip file downloaded.
Nothing difficult here.
Place the downloaded .zip file to the root of your SDcard.
Install the custom kernel, explained in previous tutorial.
Enter Recovery(while booting, when screen gets brighter, press Volume Down button until phone enters Recovery).
Make factory reset, wipe cache partition and clear Dalvik Cache(under Advanced).
NB! Do NOT make format /system, because some ROMs require files from system folder and installation will not finish if files are not available. Then you have to install stock ROM again.
Choose install zip from sdcard, pick the downloaded .zip file on your SDcard.
Wait for it to finish and reboot your phone.
13. Relocking bootloader
When you return to stock and/or need warranty back, you will need to relock bootloader. First install stock ROM and kernel and then relock bootloader, else you will have problems. Depending on the unlocking method, there are 2 ways to relock.
TEST POINT METHOD
Start S1 Tool and click Restore button. Should relock the bootloader automatically.
OFFICIAL METHOD
Will not work on test point method, because bootloader was patched there ant not unlocked.
Make sure you have Flashtool installed.
From the downloads section, download Xperia_Relock_Bootloader.zip file.
Extract the package, there is a .ftf file.
Flash the .ftf file with Flashtool.
Bootloader is locked again
14. Preparing for Ice Cream Sandwich update
ICS update is already released. You might want to know, what you need to do to get the update. Make sure, that you have
a working Xperia 2011 device
with stock ROM and stock kernel installed(if you install via PC Companion or SEUS)
and locked bootloader(if you install via PC Companion or SEUS).
Root access doesn't matter(according to current information), whether you have or not. It is lost after update anyway.
PC Companion and/or Update Service installed on your computer.
Drivers working for your phone.
Official update will only be available via PC Companion and Update Service. But you can also use Flashtool to install ICS.
15. Overclock/undervolt/underclock guide
Want to give your phone a small performance boost? Or save battery?
WARNING! The following is done fully under your own responsibility! Overclocking is a dangerous process and doing it without knowledge will end in FULL BRICK! Be careful with what you do and proceed only if you fully understand the process!
You need root, unlocked bootloader and custom kernel, that allows OC/UC/UV, installed.
Install app to edit the CPU, for example SetCPU, SetXperia, NoFrills CPU Control or another one.
Open the application on your phone.
CPU Frequency is the clock, how fast your CPU works. The faster it works, the more power it uses, more heat is generated, info is faster calculated.
CPU voltage is how much power the CPU receives. It can affect, how CPU works. Manufacturers set it to high enough for CPU to work properly. You can set it lower to save battery, however you might occur problems with your phone!
Search on internet for more information about overclocking to know more about it.
Do everything carefully, as a small mistake could result in serious problems(for example, FULL BRICK due to motherboard damage). Repairing can cost more than phone itself.
16. Optimizing your phone's battery life
Tips, how to increase the battery life of your phone.
Turn off GPS, Bluetooth, WiFi, if you do not need them at that moment.
Turn off automatic sync(ronization). This can be done in Settings, but some apps also have those features inside their own settings. For that, open the application, open its settings and look there. These vary, so I can not help any further here.
Look for battery tweaks on the forum. These can be either build.prop or init.d type.
Turn off unnecessary programs, but not which start up automatically again. And do not use taskkillers.
Why? http://lifehacker.com/5650894/android-task-killers-explained-what-they-do-and-why-you-shouldnt-use-them
Turn off your phone, if you do not need it overnight.
Set display brightness to as low as possible, as high as necessary (depending, where you use your phone).
Remove unnecessary widgets. They require also some juice to keep on working and the more there is of them, the more juice is used. If the widgets on the home screen are not necessary, remove them.
If you do not use your phone for a longer period, use Airplane Mode, if it is possible. It saves a lot of battery by turning off all radio functions on your phone.
If you do not use mobile internet provided by your operator (that means you only use WiFi to go on the internet), then you won't need 3G either. Set your phone to GSM only, it saves quite a few % per day.
Underclock/undervolt your phone's CPU, if you have custom kernel that allows it. Do it carefully and only at your own responsibility!
NB! If you underclock/undervolt, do NOT “Set on Boot” until you know that they are going to work. Otherwise if it doesn’t work and your phone randomly reboots, you will get into a boot cycle (not a bootloop) because you put them in “Set on Boot”. You must test before you should do this.
Use apps like BetterBatteryStats or Android's stock Battery Info to find out, what is consuming battery.
And of course, just to mention it - batterystats.bin file has NO influence on battery life!
Tutorials | Firmware | FAQ | First Aid - Updated 13/6/2012
XX. Downloads
Stock firmwares, ftf file is inside the zip/7z archive(except PreRooted firmwares)
4.0.2.A.0.XX type - Android 2.3 Gingerbread
4.1.A.0.562 - Android 4.0.3 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
4.1.B.0.431 - Android 4.0.4 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
Xperia Mini (ST15i)
4.0.2.A.0.42 - http://www.mediafire.com/?uboo3lrdxnoeldn
4.0.2.A.0.62 - http://www.mediafire.com/?zad88cn2n78ashv
4.1.B.0.431 - http://www.mediafire.com/?wot47vumhstlc4h
Xperia Mini Pro (SK17i)
4.0.2.A.0.42 - http://www.mediafire.com/?hevz3x5w9pqt24q
PreRooted 4.0.2.A.0.69 - http://www.mediafire.com/?desy0bkka1b44g0 - Flash via Recovery
4.1.B.0.431 - http://www.mediafire.com/?j0bdx06zz5skvzt
Xperia Mini Pro (SK17a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?433tco785pj1y69 - Branded Mexico Telcel firmware
4.0.2.A.0.62 - http://www.mediafire.com/?zykznaar0yjxbp5
4.1.B.0.431 - http://www.mediafire.com/?9d2wcbfqly4lkf3
Xperia Active (ST17i)
4.0.2.A.0.42 - http://www.mediafire.com/?3zm7iss0sid94wr
4.1.B.0.431 - http://www.mediafire.com/?7hsrd2wmuqgmmq1
Xperia Active (ST17a) - "a" model
4.1.B.0.431 - http://www.mediafire.com/?yvjnt0qctun9t6j
Xperia Live with Walkman (WT19i)
4.0.2.A.0.42 - http://www.mediafire.com/?5ahb85ir7ni0i06 - NOT WORKING
4.0.2.A.0.58 - http://www.mediafire.com/?4deeznrbldz886u
4.0.2.A.0.62 - http://www.mediafire.com/?ervpg54922b9c0p
4.1.B.0.431 - http://www.mediafire.com/?xklhl2uk1itk0ey
Xperia Live with Walkman (WT19a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?adigb2qgvpf0o1s - NOT WORKING
4.1.B.0.431 - http://www.mediafire.com/?4t3mm7dvm01v3mh - NOT WORKING
Xperia Ray (ST18i)
4.0.2.A.0.42 - http://www.mediafire.com/?0oi9t2m0z5p8a9y
4.1.A.0.562 - http://www.mediafire.com/?1lh84f1nyzoz883
4.1.B.0.431 - http://www.mediafire.com/?2j7i7rruqxnui3q
Xperia Arc (LT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?8aa5x52vc9dc25l
4.0.2.A.0.62 - http://www.mediafire.com/?0ann64yqnl4ei62
4.1.B.0.431 - http://www.mediafire.com/?pzr6phfd19xgbva
Xperia Arc S (LT18i)
4.0.2.A.0.42 - http://www.mediafire.com/?9mz2rhdouu6ggtk
4.0.2.A.0.62 - http://www.mediafire.com/?gn6y626km6nryi7
4.1.A.0.562 - http://www.mediafire.com/?9at03bbhdf72h3h
4.1.B.0.431 - http://www.mediafire.com/?20z5t5tg3dgbugz
4.1.B.0.587 - http://www.mediafire.com/?rhr59r4o6oarnfx
Xperia Neo (MT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?4qy6vd4ndbfy8wy
4.0.2.A.0.62 - http://www.mediafire.com/?4apn8hchshmqq07
4.1.B.0.431 - http://www.mediafire.com/?6i2ihiint7tfl79
Xperia Neo V (MT11i)
4.0.2.A.0.42 - http://www.mediafire.com/?8bwwe8m6c49vs4t
4.0.2.A.0.62 - http://www.mediafire.com/?elicesjb6aerb7i
4.1.A.0.562 - http://www.mediafire.com/?aao25nnf30rcs50
4.1.B.0.431 - http://www.mediafire.com/?84d4w462qdfk44a
Xperia Play (R800i)
4.0.2.A.0.42 - http://www.mediafire.com/?cne2yvrtcu3ccvn - NOT WORKING
Xperia Pro(MK16i)
4.1.B.0.431 - http://www.mediafire.com/?8jdu5dkhlm4psoc
Kernel Installation Package for Xperia phones - http://www.mediafire.com/download/b8gz98ct96makyx/Kernel-Installation-Package.zip
Unbricking Xperia 2011 Package - http://www.mediafire.com/?s166qsg8qaaxc43
Relocking Xperia Bootloader Package - http://www.mediafire.com/?1an09qoq5yq4b5y
XX. Frequently Asked Questions
Q. I just installed custom ROM, but phone is frozen at the logo!
A. Did you install custom kernel, which is confirmed to be working with that ROM? If you did everything correctly, it might take a while, because at first boot new caches are created.
Q. Flashtool won't install stock firmware, gives this-and-this error.
A. Make sure phone is in flashmode(turn off, hold down Volume DOWN, connect USB cable). If yes, make sure, that correct drivers are installed. If yes, post here with FULL log, and I will take a look.
CREDITS
http://forum.xda-developers.com/showthread.php?t=1093062 - Android dictionary
http://forum.xda-developers.com/showthread.php?p=18805532 – zergRush rooting method by DooMLoRD
http://forum.xda-developers.com/showthread.php?t=1346190 - SE Tweak Installer by quangnhut123
http://forum.xda-developers.com/showthread.php?t=1426912 - Original tutorial by hansip87
FreeXperia Team for the unbricking file
http://forum.xda-developers.com/showthread.php?t=991276 - V6 Supercharger
http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 - Kickass Kernelizer by zeppelinrox
http://forum.xda-developers.com/showthread.php?t=1477440 - Stock firmware list for 2011 Xperia phones by benji.berg
http://forum.xda-developers.com/showthread.php?p=24882250 - DooMLoRD ICS Rooting method
http://www.xperiablog.net/2012/04/16/root-for-android-4-0-ics-xperia-update-now-available-guide/ - Original Xperia ICS rooting guide
http://forum.xda-developers.com/showthread.php?p=26914104#post26914104 - Android 4.0.4 rooting guide by puppet13th
All users, who gave me ideas for this topic.
All users, who have shared their stock firmwares.
Everyone else, who I may have forgotten.
Thanks for the nice post. There should be a section for flashing kernel via Fastboot and Flashtool too.
BTW for installing ClockworkMod Recovery into the system partition, I highly recommend downloading the Xperia CWM Auto-Installer. It's right straight on Google Play and also absolutely free, just one click and everything will be done.
can't wait to see it done
acb123 said:
Thanks for the nice post. There should be a section for flashing kernel via Fastboot and Flashtool too.
BTW for installing ClockworkMod Recovery into the system partition, I highly recommend downloading the Xperia CWM Auto-Installer. It's right straight on Google Play and also absolutely free, just one click and everything will be done.
Click to expand...
Click to collapse
Already planned to add kernel and custom ROM flashing.
Will check out that Auto-Installer.
You should also add a 2 more sections on how to Flash stock ROM and Relock the Bootloader just incase anyone messes up. Also if needed, add a Unbrick method . Great thread and can't wait for more!
Plus, when you root through ZergRush method, doesn't that automatically install Busybox?
BudgyN1 said:
You should also add a 2 more sections on how to Flash stock ROM and Relock the Bootloader just incase anyone messes up. Also if needed, add a Unbrick method . Great thread and can't wait for more!
Plus, when you root through ZergRush method, doesn't that automatically install Busybox?
Click to expand...
Click to collapse
Unbricking is already planned, thanks for other ideas
As for the rooting, I am not sure. Could anyone confirm it, I used that method long ago, can't remember.
Sent from my WT19i using xda premium
I just read the ZergRush method thread and using it does install Busybox
Sent from my SK17i using XDA
sk17i
Root / Unroot Sony Ericsson Xperia 2011 v1.5 without unlock bootloader
http://forum.xda-developers.com/showthread.php?t=1346198
sk17i(4.0.A.2.335), root OK, no sw downgrade was needed
akloms said:
Root / Unroot Sony Ericsson Xperia 2011 v1.5 without unlock bootloader
http://forum.xda-developers.com/showthread.php?t=1346198
sk17i(4.0.A.2.335), root OK, no sw downgrade was needed
Click to expand...
Click to collapse
Downgrade is only needed if you have 4.0.2.A.0.62 or 4.0.2.A.0.69.
Also, I am unaware of this firmware, never heard/seen.
Sent from my WT19i using xda premium
Information for return from custom Kernel/ROM to stock one?
Only need to re-flash with WotanServer and re-lock the bootloader (before or after the flash)?
Thanks
m4x23 said:
Information for return from custom Kernel/ROM to stock one?
Only need to re-flash with WotanServer and re-lock the bootloader (before or after the flash)?
Thanks
Click to expand...
Click to collapse
Yes, just reflash with WotanServer and then relock bootloader if you want completely clean stock.
Will add guide about that also, thanks for tip
More stuff will come in the following days, been a bit busy.
Can you please post how to install Supercharger and KAK next? I read those threads and just getting confused how to install them. Really want to optimise my phone but not mess it up.
Thanks
I think you should add some basic concepts like what is fastboot or why do you need it difference between flashmode and fastboot and how to access them. What is the bootloader and what good or bad will it do to unlock it. Most new users don't know all that.
If you like to I can help you adding some concepts just let me know.
Oh and adding the info for the processor governor and i/o scheduler will be good to.
Hi there guys! By the way excelent tutorial, but I have an question!
I did the unlock bootloader by the test point method with s1tool!
I had Bootloader unlocked allowed: No and I still have it!
Here's the S1LOG: http://pastebin.com/XSDQ2iVf
Is my bootloader unlocked?
Please help,
pedrorubster
pedrorubster said:
Hi there guys! By the way excelent tutorial, but I have an question!
I did the unlock bootloader by the test point method with s1tool!
I had Bootloader unlocked allowed: No and I still have it!
Here's the S1LOG: http://pastebin.com/XSDQ2iVf
Is my bootloader unlocked?
Please help,
pedrorubster
Click to expand...
Click to collapse
Mmmm it is hard to tell with this log can you click on identify in s1tool and upload again?? Anyway I suppose you have a branded sim locked phone right?? Then even if you unlock your bootloader you won't be able to flash a custom kernel because the fast boot mode will be locked, if you are lucky you will be able to access it, you can always try, power off your phone hold down volume up key and connect it to your PC still holding down the volume up key it should stay off with the notification led on blue.
If you are lucky and can access it then you are good to go if not you will need to pay to fully unlock your phone sorry about that.
ginryu said:
Mmmm it is hard to tell with this log can you click on identify in s1tool and upload again?? Anyway I suppose you have a branded sim locked phone right?? Then even if you unlock your bootloader you won't be able to flash a custom kernel because the fast boot mode will be locked, if you are lucky you will be able to access it, you can always try, power off your phone hold down volume up key and connect it to your PC still holding down the volume up key it should stay off with the notification led on blue.
If you are lucky and can access it then you are good to go if not you will need to pay to fully unlock your phone sorry about that.
Click to expand...
Click to collapse
Thanks! I think I will have to pay 15€ to WotanServer...
pedrorubster said:
Thanks! I think I will have to pay 15€ to WotanServer...
Click to expand...
Click to collapse
Yes, branded phones can only have unlocked bootloader via paid method.
Sent from my WT19i using xda premium
Hi..sorry if my question is off topic
I did the unlock bootloader by the test point method
I want to relock bootloader back.
Im use Restore option at S1tool and got this error:
RUNNING S1_EROM VER "r9A021"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0098/00B3"
LOADER VERSION: "R4A069"
FAILED TO FIND RESOURCE ""
Anybody can help?
KitKat for the Omate TrueSmart
Congratulations, you made it this far and managed to keep your unit alive long enough to upgrade it to the next level!
4.4.2 Changelog:
================
Fixed glitch in boot animation to make it smoother
BTLE profile and PAN profiles added
Full Settings Menu
Functional Accessibility Menu
Updated Wi-Fi Drivers, now supports ip6, ip4, and low-power mode
Updated GPS Drivers, lock-on after initial lock and AGPS update should be quicker
Kernel updated from 3.4.5 to 3.4.67, supports SELinux
Unlocked bootloader and insecure kernel allows for root access through SU
Google Play Services included
Google Talkback/Voice Search integrated
Fixed glitch where Voice Search would not complete spoken sentences
TWRP updated to 2.8.3.0 with full features and MTP support
Camera now operates at 5MP/720P without force closing
Security holes have been closed
MALI 400 drivers updated
Battery management integrated; after first boot battery readings should be accurate
Sound issues fixed; microphone should no longer sound muffled
Soft reset implemented, holding both buttons for 10-15 seconds should power down or reset unit
ART mode implemented, allowing for faster and more efficient performance
Known Issues:
=============
Sensors are non-functional until updated drivers are available (if they become available)
Settings is not accessible from status bar icon
1900MHz units are unable to access 3G data currently (if a modem becomes available this should change)
Bluetooth connectivity may occasionally drop out depending on data load
APNs are not automatically added
IMEI may be lost or corrupted after installation
Instructions:
=============
REQUIRED PROGRAMS:
1) SP FLASH TOOL
2) MTK DROID TOOL
3) WINDOWS OS XP or HIGHER
The All Tools suite for MTK devices can be found here:
MTK All Tools Suite
****** You must install the preloader drivers for your device using the 32-bit or 64-bit installer (dpinst) for your operating system before you continue. ******
I suggest making a full backup of your device either in TWRP or in MTK DROID TOOLS (1:1) to preserve valuable data or in case of a failed upgrade. You should always back up your IMEI/NVRAM in DROID TOOLS for safe-keeping and this is no different.
Download the full set of factory images here:
Omate 4.4.2 Factory Image RAR
Extract the contents of the ZIP file to a known directory and proceed to the next step.
Next, navigate to the Settings menu on your Omate TrueSmart and, under Accessibility, disable Quick Boot. This is the only way to enter Download mode reliably. With that completed, power down your watch.
Finally, open the scatter file (mt6572_scatter_emmc.txt) found in the directory you extracted the ZIP file to in SP FLASH TOOL and check to make sure each file is present. You may need to manually add the system.img and recovery.img. To do this, double click on the empty box and select the file.
Once you've made sure each file matches, go to the drop-down menu where it says "Download" and select "Firmware Upgrade". Take one last look to make sure every file is selected and press the Download button on the top left of the screen.
With the watch powered off, go ahead and plug it in. THEN WAIT. It will take between 5-10 minutes to fully upgrade your unit. You should see a red bar, then green, then purple, then yellow. If you get any error that says "BROM DLL ERROR" note down the error number and send me a message. If it gives you a green checkbox, you're done with this step.
Now you're ready to boot the watch. Press and hold the power button until it powers on. The first boot will take approximately 5 minutes to complete while it assembles all of the information. Once it finishes, power down the watch. Hold the home (bottom) button and press and hold the power (top) button simultaneously (at the same time). You'll see a recovery menu. Press the power button to boot into TWRP. From there, select "Wipe" followed by "Factory Reset". You will want to reset the watch to factory settings. You can either make a backup or go ahead and reboot the system.
Congratulations! You should now be on Android 4.4.2 for your Omate TrueSmart.
NOTES
=====
If you're missing APN information I suggest you either restore previously saved APNs or add them manually if they disappear. Currently 3G data will not work on 1900MHz units.
This firmware was designed for UMEOX smart watches operating on the x201-series MT6572 chipset. I am not responsible if you damage your watch because you flashed the firmware incorrectly or to the incorrect watch.
If you have any questions as to whether your watch is compatible, please message me.
It is IMPOSSIBLE to brick your watch if you are flashing this firmware. If for some reason you think your watch is bricked or you feel uncomfortable flashing this firmware you are welcome to send your unit to me (if you pay shipping) or I am available to help over Chrome Remote Desktop to flash it for you.
If you are having issues getting the firmware to work, please send the following information to me:
Watch Manufacturer
Date Received
Last Known Firmware
Case Material
And I will answer on a case-by-case basis to help you troubleshoot. I never make guarantees but I promise to help as much as I am able.
Finally, please take the time to thank the brave soul who voided his warranty to get me the prototype firmware for this. I won't reveal his name for security's sake, but he obtained a developer unit from another company who uses the x201 chipset and was kind enough to upload the system dump in September of last year. I would have presented this sooner to you guys, but until the method for flashing the S8 firmware was released I had no idea why I couldn't get it to work.
SPECIAL THANKS
==============
Laurent LePen, for giving me the tools from UNOVA to make this possible
@Dees_Troy, for having the patience to flash the firmware, assemble a system image, and update TWRP
Derek Serianni, for flashing his watch 42 times to test the firmware
Christos Vorkas, for testing SIM functions and the early firmware
@AdamOutler, for advice operating Linux and troubleshooting errors
The Anonymous Firmware donor, who voided his warranty and bravely e-mailed me about 1.5GB worth of files
XDA, for always having that clinch moment where someone has a breakthrough that helps the rest of us
KNOWN COMPATIBLE UNITS:
IconBit:
Callisto 100, 300
SimValley:
Pearl AW414, AW420/1
UMEOX
X201
Omate
TS-1/TrueSmart 512MB/4GB Edition
TS-1/1900MHz 1GB/8GB Extreme Edition
TS-1/2100MHz 1GB/8GB Extreme Edition
For Root, download Chainfire's latest SuperSU package and flash in TWRP:
SuperSU 2.44
Derek Serianni, for flashing his watch 42 times to test the firmware
Click to expand...
Click to collapse
I think that number is a lot higher actually..... but, 42 is quite fitting as this is now the answer to the ultimate question...
It has been an exciting couple of days testing and flashing.
Despite all the trial and errors, not once did the watch become unrecoverable.
If you load Google Now Launcher and the latest Google Search APK (and setting it up properly) you can use the "Ok Google" feature from the lock menu as well as in the OS.
I stopped wearing my LG G and am now wearing the TS daily....
Kudos for all the hard work!
I knew there was light at the end of the tunnel!
D.
Great job!
hi dan,
i have tried to flash this to my EU 1/8G Pre May Omate TS.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - EU Ensec Stock 0706
Case Material - Steel
A few questions:
1) the downloaded KK Omate rar file does not include UBOOT.BIN or a BOOT.IMG file. Am I supposed to leave it blank or use the UBOOT / BOOT IMG from my current Omate's backup?
EDIT: I have tried using the UBOOT.bin and BOOT.IMG from another KK thread but still run into the same "CheckSum Failed" error i mentioned below: http://forum.xda-developers.com/showpost.php?p=57433563&postcount=189.
2) under FLash Tool: the ANDROID file is usually blank - i have selected system.img from the rar file for the file to be flashed for this. Is this correct?
3) When flashing via FlashTool, about 27 seconds into the flash (i see a RED Bar, then it changes to a couple of BLUE "Read Back" bars), I keeping getting a error saying "CheckSum Failed". I have tried redownloading the KK Omate rar file and trying again but to no avail.
EDIT: I have tried with different ports, different cables, including cleaning the Omate TS's ports with no luck. Just prior to the flash, i was able to do a full backup so it does seem strange and does not seem specific to the cables/ports/contacts on the TS.
UPDATE: Seems to be working - TRY Flash Tool v3.1332 instead of the latest V5.1352. It is now flashing fine as mentioned by Dan.
FINAL: My TS boots up fine with KK now! If you face the checksum error as i did, try using SP Flash Tool v3.1332 instead! - LINK HERE: http://androidxda.com/smart-phone-flash-tool
Any advice on the above?
NO UBOOT
Trying to flash this on my Omate 2100 unit but the UBOOT is missing for me? Got the system.img and recovery.img added but no uboot.
I am also not sure what to select as "BOOTIMG".
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Caboose1979 said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
Mike? hehe did you get the same error i had? with the CheckSum failed as well?
Isn't the baseband included under "0 Needed files -> NA/World Baseband"?
I can not check if valid files. My TS is not booting/reacting to Flash tool anymore...
Not sure if I did it correctly but because I could not find the boot.img within the supplied files I took the boot.img from the other kitkat rom here on xda. Have at least a working TS now .
Only problem right now is that the home button is not functioning as the home button. It sets the volume to max.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
I had the same issue as well!
Thanks. Works well like the other early ROMs and is a bit better prepared including Google Play etc. Can we remove the extra apps like QQ etc from the image for a future release? Edit that might have been my fault from not wiping after flashing although I was pretty sure I had already removed them from the ROM whilst creating a flashable zip.
When turning on Wifi I do get an NVRAM error initially in the list of Wifi items. It fairly quickly finds real ones and it connects fine to my AP.
I have the issue with the second button turning up the volume too. There is a fix in the other thread for this.
Also I had to manually select system.img, the recovery, uboot.img and boot.img (the latter two weren't in the archive so I took from the X202 image in the original KK thread).
Glad to see Omate somewhat taking credit on Facebook. It seems I'm banned on Facebook from recently posting after commenting that they probably shouldn't be taking credit for this. The initial announcement a few days back has 14 missing/hidden comments. Oh so childish LLP - I'm sure you're reading.
I'd like the sensors if possible, mainly for a shake/rotate to wake up function..
---------- Post added at 11:43 PM ---------- Previous post was at 11:38 PM ----------
Caboose1979 said:
could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
I'm going to take a look at doing this when I get a chance in the next couple of days. I had a basic one working with just system and boot images of the KK ROMs. It should be possible but I'm kinda new to this so not sure if there are any limitations when flashing everything like this. I do need to make sure I know all of the device names to flash.
Hi Guys,
Not sure where I am going wrong, can't make head nor tails so far.
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
On from that i am also missing the .img files that the others are.
sorry to be a hassle, i will do my best to work it out, but just need a bit of help getting off in the right direction please,
also i haven't done any other flashing etc with my truesmart, is there anything i should be doing prior for brick protection?
it is a 2100mhz model
Cheers
burlyoaf said:
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
Click to expand...
Click to collapse
MTKDroidTools is different to SP Flash Tool. They are 1 and 2 respectively in the All Tools folder.
Follow the instructions exactly particularly the order. Turn the watch completely off (disable Quick boot), click download and *then* plug the cable in.
Quick Update:
My EU 1/8G Omate TS-1 Pre-May is up and running fine (see my earlier post for some tips / advice based on the issues i had).
1 major issue as below:
However, under Baseband - it shows unknown, and similarly in IMEI - it also shows unknown.
i tried to flash the old 2100 World Baseband.zip in TWRP, but no luck,
tried to use MKT Tools to restore my NVRAM but no luck either (just shows install\data\nvram) and then nada.
minor issue: home button is defaulting to UP Volume instead of HOME function. I will try to flash the FIX_HOME.zip in the other thread and report back.
any advice Dan or anyone else who has theirs working?
If it says uboot, that's the lk.bin.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
Stop with the attentions. The baseband is included. I've had at least 5 people flash it with no issues.
IF you are missing a baseband, sit tight. Try flashing the UNOVA system image, then flash this again.
IF you are having checksum issues, either use an older version of flash tool OR format and flash the stock firmware.
The LK and Kernel must have been a goof on my part. I'll fix that.
Haven't been able to find anything on this model as of yet, looking for info for rooting and any possible roms/hacks. also asking for thumper1436 who's original thread is http://forum.xda-developers.com/general/xda-assist/please-help-stock-nextbook-10l-quad-t3254936 --there (sorry, not familiar with proper tagging features for the bulletin boards just yet).
thanks for any info in advance!
found some hope from https://www.youtube.com/watch?v=baIhaJ0Zz5U . not the exact model but a starting point maybe? we'll see.
::edit:: i'm an idiot. after mulling about and using the commands in the video comments, I kind of figured it out. booted into bootloader, flashed the boot and recovery img's via fastboot, and so far so good. rebooted into recovery and twrp is up (yay). now to work on rooting (hopefully as easy as installing the zip files through twrp). worst thing that can happen is I brick it. wish me luck.
oh yeah, android 5.0 kernel version 3.10.20-x86_64byt build v 1.0.7
okay, so attempted backup via twrp but it failed. figured wth, flashed recovery zip and super su zip from link in youtube video ( https://www.youtube.com/watch?v=baIhaJ0Zz5U ). after rebooting, went to play store and installed a root checker, and viola. so root achieved.
keep in mind that using twrp wouldn't work without keyboard attached (which is annoying). controls are normal, though throughout the process the screen goes portrait mode instead of landscape, so figuring out "mouse" controls is wonky but doable. after root, using the touchscreen is all but gone (very very buggy, not sure how to fix as of yet). if i could find a recovery image from mfg it'd be great (already emailed them about it, but very very doubtful it'll show up).
tl;dr
root is possible, but makes system buggy.
DO THIS AT YOUR OWN RISK! YOU ARE RESPONSIBLE IF YOU BRICK YOUR TABLET! WARRANTY IS VOID, ETC.
-----please do a clean install/wipe/factory reset first. it's always a good idea and can save you the headache from bugs that can occur from not doing this. please. google is your friend if you're a bit lost on how to do anything referenced in this "guide" ----
I take no claim of ownership of the files used in this process. respect goes out to the owners/originators.
1) install working adb drivers (through android sdk or however). I went with installing from here . don't forget the java crap (link is on this page too, just read the instructions).
2) download twrp and recovery files from here
3) i downloaded the nocturnal adb stuff as well from here . Was easier to keep files organized imo.
4a) extract files from both and put files from step 2 into the same directory as files from step 3 ( will look like image from looky looky when done right). don't forget to copy the recovery.zip and SuperSU246.zip to the root of an external sd card, going to need these in the future.
4b) i forgot about the developer options thing. if you're working with the tablet already booted up like normal, you have to enable developer options and turn on usb debugging (there's all the info on that in the youtube video referenced from the post above, or by google-ing it).
5) hold down shift and right click in window, select "open command window here". if tablet is loaded up like normal, you'll type in "adb devices" to make sure the drivers installed okay (it'll show a device if all is done right). if tablet is already in the bootloader, type in "fastboot devices" and it'll show a device if all is done right. google is your friend on how to get into the bootloader, or you can always load up the tablet, verify the adb drivers are working, and go to step 6.
6) type in "adb reboot bootloader". when it loads up, type "fastboot flash boot boot.img" and hit enter. When that completes, type in "fastboot flash recovery twrp_recovery.img" and hit enter. all should show okay (mine had a data error from the backup, didn't seem to effect much, though i'll be going back and redoing this with a clearing of data/factory reset first that will hopefully kill the buggyness of the touchscreen.
7) use the volume down button to change the option to "recovery mode" and select with power button. once there the fun begins.
8) as stated before, using the mouse pad seems the only way to go. up is up, down is down. the screen however is turned on it's side this way.
go to the "install" button and click on it. navigate to the root of the external sd card (click the storage button at the top, change to external_sd) and click ok. should have to just scroll down and select the recovery.zip file. click "add more zips" button and select the SuperSU246.zip file. click and drag the "swipe to confirm flash" button and release. wait for confirmation of success.
9) go back to main menu (I used the navigation buttons on the physical keyboard) and reboot into the system.
that's all there is. as stated, it is buggy as hell and the touchscreen is all buggered up. but using the keyboard/touchpad seems to work. not sure of too many other bugs yet as this is fresh off the press and I haven't done anything else with the tablet since doing this (besides installing the root check program from the play store and running it to verify it worked.
hope this helps someone =)
::edit:: damn this is a little confusing to read, sorry about that. first time attempting a guide like this.
device info from skipsoft android toolkit.
DEVICE INFORMATION
==================
Product Manufacturer: Yifang
Product Model: NXA101LTE116
Model ID:
Device Type: NXA101LTE116
Device Characteristics: nosdcard,tablet
Product Serial Number: YFGV0715030938
Build Description: nxm1017bapl_64-user 5.0 LRX21V 20150708.171530 release-keys
Build Date: Wed Jul 8 17:17:24 CST 2015
Hardware: nxm1017bapl
Board Platform: baytrail
Build Version Release: 5.0
Build ID: LRX21V
Bootloader: unknown
Build PDA:
CSC Sales Code:
Region Code: US
Ro.secure Level: 1
Ro.adb.secure Level: 1
Selinux.enforce Level:
Selinux Level:
Alarm Alert: Alarm_Classic.ogg
Notification Sound: pixiedust.ogg
Ringtone: Ring_Synth_04.ogg
------------------------------------------------------------------------------------
Boot Image Status is: SECURE [based on ro.secure value]
Note: This is only an indictation if the boot image files have been modified
------------------------------------------------------------------------------------
::edit:: info was prior to rooting device.
Do you happen to have a stock image or a backup available?
daleguthery said:
Do you happen to have a stock image or a backup available?
Click to expand...
Click to collapse
unfortunately no. i tried emailing the mfg to no avail (they claim they don't have the image files to restore them). haven't tried doing a factory restore yet, though i doubt that'd help. right now i just use it as a "laptop" with using the track pad instead of the touch screen. still a work in progress, just been busy with life happenings. will update if i can find out more (or if i manage to get my hands on another untouched unit that i can try and dump or something).
I have also tried contacting the mfg, and they told me the same thing. I read somewhere that this tablet was actually made by eFun. The stock rom for the model without LTE will work on this tablet, however there are somethings that don't work correctly, the first being enabling LTE and recognizing a SIM card. The others are camera orientation, and screen rotation is always upside-down.
daleguthery said:
I have also tried contacting the mfg, and they told me the same thing. I read somewhere that this tablet was actually made by eFun. The stock rom for the model without LTE will work on this tablet, however there are somethings that don't work correctly, the first being enabling LTE and recognizing a SIM card. The others are camera orientation, and screen rotation is always upside-down.
Click to expand...
Click to collapse
I have the same tablet. I will be attempting to root.
The lack of custom roms for our device is depressing, there aren't enough developers for the M4 aqua and while some have moved on to other devices, others don't share their REAL sources and fixes. So what i propose is that we all join forces and do it ourselves, the more people the better it brings different points of view and consequently faster fixes, so for those that are interested here are the prerequisites:
1. A computer
2. A linux distro (most guides will advice you to go for ubuntu or a buntu based distro personally its not my cup of tea, i use gentoo but linux is about choice you choose what suits you. Also if you want to keep your windows you can either dual boot(recommended) or just use a virtual machine which depending on specs it can be slloooww).
3. A starting point (most people don't even try to compile android because they wont even know where to start from, thankfully sony isn't as bad as others and even provides detailed information on how to compile android for their devices, so i suggest to start here http://developer.sonymobile.com/kno...aosp-marshmallow-for-unlocked-xperia-devices/ )
4. Time (compiling times can take very looonnnggg)
5. Patience ( yeah a hell lotta of it)
Still interested?
We can use this thread to post compiling errors , bugs, errors and any android developing related questions, if instead of aosp you want to jump straight to cyanogenmod the instructions are very similar just replace "repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.1_r10" with "repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0" xda also has some very useful threads we can use here are a few:
1. Compiling roms:
CM - http://forum.xda-developers.com/showthread.php?t=2060017
PAC - http://forum.xda-developers.com/showthread.php?t=2662325
2. Debug
Create logs - http://forum.xda-developers.com/showthread.php?t=2185929
Understand them - http://forum.xda-developers.com/showthread.php?t=2274119
Every great dev had to start at some point this might be start of some great devs (we need them), so lets start compiling and bring the marshmallow to the tulip!!!
We have a few custom roms that just need bug fixes. We will get better as time goes on. And would we see a rom of yours anytime soon?
I don't find the m4 binaries in this page http://developer.sonymobile.com/knowledge-base/open-source/open-devices/list-of-devices-and-resources/
Hello guys, as much of you know, I tried so many times to compile roms for our device, but never had success. My device for now enter in a "bricked fastboot" mode, and in flashmode Flashtool say that the device have debugging off. Totally bricked. But, I will never give up with my work for this device. I will make roms for you guys and for my experience, also if I cannot test. So, I installed Ubuntu in my PC, I am syncing the sources and this time I will try very hard! Thanks CarDGee for your post, it will be helpful for errors.
So, what would be our requirements knowledge wise? What programming language base, etc?
Any kind of knowledge of programming language can be useful, but is not needed.
alby_var said:
Hello guys, as much of you know, I tried so many times to compile roms for our device, but never had success. My device for now enter in a "bricked fastboot" mode, and in flashmode Flashtool say that the device have debugging off. Totally bricked. But, I will never give up with my work for this device. I will make roms for you guys and for my experience, also if I cannot test. So, I installed Ubuntu in my PC, I am syncing the sources and this time I will try very hard! Thanks CarDGee for your post, it will be helpful for errors.
Click to expand...
Click to collapse
I think at this point it would be smart to collaborate on a custom rom (probably CM 12.1 because it is closest to stable) so we have a base to develop more roms.
For now I'm working to build AOSP 5.0
I followed the instructions to build AOSP at developer.sonymobile.com
At point 4. it say
Find the software binaries for the device you want to use on Sony’s AOSP for Xperia devices
Click to expand...
Click to collapse
Now i have downloaded the binaries for the M2. It have the Kanuti and Tulip folder inside.
Can i use it for build or do i have to extract the files from the device?
Second question is. I can remove other devices from local_manifests.xml right?
You can also use GitHub sources and put them into android sources with git clone, with this method also if you edit files, you'll not have problems with repo sync.
@dani020110 download the Z5 ones inside the zip you will have kanuti and tulip folders as well.
@alby_var what do you mean "bricked fastboot" is it constantly with blue led on? have you tried holding powerbutton + vol up until it vibrates 3 times?
@jefins although its a plus to know C java etc.. its not a requirement i am a strong believer that you learn by doing it.
@jtg01 yes use the ones from the zip also take a look at this repo https://github.com/SonyAosp you can find the binaries there under platform_vendor_sony and platform_vendor_qcom.
Now i regret not having done one of those "Reserved" on the second post.....
@alby_var what do you mean "bricked fastboot" is it constantly with blue led on? have you tried holding powerbutton + vol up until it vibrates 3 times?
..
Click to expand...
Click to collapse
The device , on a pc without drivers is recognized as qhsusb_bulk. It is recoverable, but any tool doesn't recognize the smartphone.
On a pc with all drivers it is recognized sometimes as SOMC FLASH DEVICE, other times in SEMC FLASH DEVICE. Also this is recoverable, but Flashtool says that the device have debugging mode off. (I cannot boot to the rom to activate it.)
And the only led that the device show is red, it bright up 3 times only when the battery is at 0%
alby_var said:
The device , on a pc without drivers is recognized as qhsusb_bulk. It is recoverable, but any tool doesn't recognize the smartphone.
On a pc with all drivers it is recognized sometimes as SOMC FLASH DEVICE, other times in SEMC FLASH DEVICE. Also this is recoverable, but Flashtool says that the device have debugging mode off. (I cannot boot to the rom to activate it.)
And the only led that the device show is red, it bright up 3 times only when the battery is at 0%
Click to expand...
Click to collapse
Do you have the correct flash and adb drivers on your pc? My second phone is a xperia E4.i had the same problem with SEMC and SOMC.i thought that it was bricked but the problem solved when i installed adb and flash drivers from the flashtool drivers file.
I installed all drivers that is on the Flashtool Folder trought the exe, but Flashtool not start flashing...
So i compiled the sources and got a system.img and a userdata.img in out/target/product/generic ?
I think there have to be a boot.img. Do i have to compile the kernel as well? Cause instructions on sony developer say the repos contain a precompiled kernel.
@alby_var: which version of flashtool do you use? Had also problems to flash firmware on newest version. So i installed Flashtool Version 0.9.19.7. With that it worked fine.
@alby_var try the linux version of flashtool
@jtg01 there must be something wrong because it should be out/target/product/e2303 or out/target/product/tulip did you choose our device after source build/envsetup.sh && lunch? because i believe you just compiled generic android.
Compiled android 6 for 2303, attached the Make log Below. (Pure Sony AOSP)
yet to flash the images and check.
made a small change, the userdata.img is for 16GB as i have a M4 Aqua Dual (E2363) the device should be able to boot up, will add logcat when i have it.
Lots of warnings but was able to make successfully
open the log in notepad++
Edit: First attempt to boot, loops at Sony logo.
will make fresh and check again
@jtg01 there must be something wrong because it should be out/target/product/e2303 or out/target/product/tulip did you choose our device after source build/envsetup.sh && lunch? because i believe you just compiled generic android.
Click to expand...
Click to collapse
Yeah there was a problem. Now it compiled all img's . But userdata.img has only 70 Mb. System is 900 Mb.
Should i flash this?
Edit:
Flashed it got bootloop. Can't take a logcat cause it restart at Sony logo.
But i get a kernel_boot_log. There are multible errors. Maybe someone can help me with that.
Guys I not know how to adapt device sources to the rom for that I am building.. Can anyone please help me?
@RohitBopnna and @jtg01 for some strange reason newest firmware doesnt allow you to flash custom firmware you will have to downgrade to .128 and then flash your roms i am sure it will boot, follow the instructions on Jeffreyvh aosp thread http://forum.xda-developers.com/m4-aqua/development/aosp-6-0-e2303-t3271380
@alby_var I think you should start by compiling something we already have the sources see how it goes, and then move on