Related
Tutorial includes stock firmware .ftf files for Flashtool!
Changelog:
22-08-2012 - Expanded to Xperia Arc section.
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.
Same tutorial in Xperia Mini & Mini Pro & Active section: http://forum.xda-developers.com/showthread.php?t=1568792
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
Downloads
Frequently Asked Questions(FAQ)
Yet to be added:
List of system apps and which can be removed - Gingerbread and ICS
Optimizing battery life
What will you 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 -> Sony Ericsson -> Connectivity -> USB Connection Mode
Root Explorer or any file manager that provides access to root (I personally used 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 – only firmware 4.0.2.A.58 or older
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 3 first to downgrade your firmware.
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
First update your phone to the newest firmware.
Use Flashtool to flash a ICS 4.0.3 stock firmware kernel to your phone.
Run the exploit created for 4.1.A.0.562 firmware, explained in previous tutorial.
Install back ONLY the newest kernel.
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 X-Parts.
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.
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.
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.
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.
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 and 4.1.B.0.587 - 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 - Flashable zip
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
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
4.1.B.0.431 - http://www.mediafire.com/?4t3mm7dvm01v3mh
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
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
Xperia Pro(MK16i)
4.1.B.0.431 - http://www.mediafire.com/?8jdu5dkhlm4psoc
Kernel Installation Package for Xperia phones - http://www.mediafire.com/?c0u0kf0ud5jvkhk
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.
Still needs to be edited in order to fit it for Arc/Arc S/Pro.
If you notice a bug or have an idea, let me know.
Also, critism is welcome.
If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery. - Actually, there is no need for this step. The custom kernel provided above already included TWRP 3, so this is just to show you how to flash a custom recovery. Thanks, @YasuHamed
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:
Now that you have root access, the next part is to remove bloatware but I will post this later on because I need to do some more research just to confirm it won't have FCs in the future. Removing bloatware is rather self-explanatory and depends on your personal preferences. Like me, I would delete all of Google and Sony apps to bare minimum but some people prefer leaving Google Maps or Sony Smart Connect on their phone. I'll see you on the next episode, to be continued...
Reserved for battery management, tips and tricks.
cglegion said:
If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:
Click to expand...
Click to collapse
the customer kernals by @khab.bros already have recovery installed,
Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.
@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...
cglegion said:
Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.
Click to expand...
Click to collapse
the way sony is behind in specs, I think in upcoming days the development side of xperia will suffer the most as the sales goes down!
in 2016 we have mobiles reaching specs such as 2.2ghz with 6gb ram and the NEWEST xperia X series has 1.5gb ~ 2gb RAM ONLY~
-DM- said:
@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...
Click to expand...
Click to collapse
You're right @-DM-, the fact that I recommend using Android SDK was the ability to install packages automatically for example the Google USB Driver though the SDK manager and not solely for fastboot functionality. Some newbies might not even have appropriate drivers installed on their machine so their device won't be recognized hence a simple problem will lead to another problem. But of course, using minimal adb and fastboot is another noob-friendly way (which is also less in size) compared to the 100mb + Android SDK. Thanks, for the heads up too and making this thread a more noob-friendly one! :laugh:
Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!
cglegion said:
Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!
Click to expand...
Click to collapse
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...
Command Prompt
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
Make sure you have unlocked your bootloader before following this guide and just to inform you again this guide is for E6883.
Yeah I figured it out, the only problem was the fastboot drives weren't installed correctly for some reason windows 10 didn't allow it, also it was having trouble finding the boot.img so I just dragged the fastboot.exe and the boot.img into the command instead and it worked.
All in all great guide, thanks.
YasuHamed said:
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...
Click to expand...
Click to collapse
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.
shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
use flahstool
---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------
use flashtool
---------- Post added at 11:34 AM ---------- Previous post was at 11:15 AM ----------
cglegion said:
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.
Click to expand...
Click to collapse
although i never liked aroma and i won't usually recommend custom roms specially for xperia... but since you have came this far,
lets say under APK foler you removed many bloatware and also updated
you must repack you SYSTEM folder (only) back to ROOM.zip (originally extracted from ftf file using ext2explorer)
then you need to apply mods,
https://www.youtube.com/watch?v=FdhUK_Ds4Fo (part 2, deleting bloatware) / finding MODS and repacking
http://forum.xda-developers.com/showthread.php?t=1363460 (tutorial about updater script modification by notepad++ )
however just remember what ever studies i did, for android 6.0.1 the prf creator wont work,
but you can try (PRF creator)
http://forum.xda-developers.com/showthread.php?t=1363460
convert your boot.img to kernel.sin and recreate your PRF creator (as mentioned above)
OR keep the custom rom ftf and BOOT.img SAPERATE as many custom roms does that
1. cynogenmod 12+
3. Miui 5 onwards
have boot+recovery file saperate and Rom saperate to flash.
the only reason i could understand is because they flash their system via recovery. if your aroma stock has xd recovery you can keep the flashable zip to install as system ORRRR keep it as FTF file to be flash and then kernal to be flashed saperate
Thanks for this guide I just wish to have root on locked BL...
Why yet another guide? Why should you follow this guide?
This is more of a future reference for myself, but might be beneficial to some other people, hence why I decided to post it.
Thanks to the "dirty cow" exploit (CVE-2016-5195), we now have a more simple way of backing up the TA partition compared to existing guides, which all relied on another exploit that involved downgrading the firmware, thus making the whole process a bit more complicated.
Unfortunately, as you can probably tell, it's still not a painless ordeal, just "less" painful. But hey, at least you have a choice.
To keep this step-by-step walkthrough guide simple and straightforward, I am focusing on just the steps and skipping the explanations.
Let's get started!
Prerequisites
Important: Your phone must be vulnerable to the "dirty cow" exploit, any firmware version with security patch level 2016-12-01 or earlier should work, such as 32.2.A.5.11. Basically, any MM or LP firmware.
Currently there is no way of backing up the TA partition on Android 7.0 Nougat firmware, you will need to downgrade to MM or earlier firmware first.
Remember to backup all your data before you downgrade, since a downgrade is akin to a factory reset. Downgrade instructions:
Follow Step 0, skip Step 1 and 2
In Step 3, download a MM or LP version firmware. For the sake of simplicity, I suggest you download the one labeled Storefront.
Follow Step 4 and 5
Done, your phone is now downgraded, skip the remaining steps. Continue with the guide as usual from Step 1
Note: If the DRM keys are irrelevant to you (TA partition already backed up/restored/lost) and would just like to root, then you can root using this guide on all firmware versions including Android 7.0 Nougat without downgrading. In this case, you can skip Step 1 and Step 7. Depending on your situation, you can also skip other parts of this guide, such as Step 2 if your bootloader is already unlocked, or in Step 5 don't wipe anything (leave all boxes unchecked) to retain your apps and data for a firmware upgrade.
Computer setup with correct drivers and adb/fastboot connection ability.
Enable USB debugging on the phone:
Settings > About phone > Tap multiple times on Build number until Developer options is enabled
Settings > Developer options > USB debugging > Toggle ON
XperiFirm for downloading official Sony firmware directly from Sony's servers
Flashtool for flashing firmware
Battery preferably more than 80% remaining, loss of power while flashing can brick your phone
Step 0 - Backup your phone (optional)
Move all your data to your SD card using the native tool: Settings > Storage > Transfer data to SD card
Use Sony's Backup & restore app to make a backup: Settings > Backup & reset > Xperia Backup & restore > More > Manual backup > Select SD card > Select content to backup
Personally, I choose everything except apps, they can be re-downloaded from the Play Store at any time, plus they take a long time to backup and restore not to mention eats up free space
Step 1 - Backup the TA partition
Download this wonderful TA Backup tool, unzip to desired location
With the phone powered on, connect the USB cable to the computer, then plug the micro USB end to the phone
Open command prompt (Start > Run > cmd), navigate to the directory where you unzipped the TA Backup tool
Run the following command:
Code:
backupTA
The tool will run and if successful, you should see at the bottom the words "TA Successfully pulled to TA_E5823.img".
TA_E5823.img is the TA partition image file, actual filename will be longer and differ for everyone so to keep it simple we'll just refer to it as TA_E5823.img in this guide.
Please check that the file is 2,097,152 bytes. If not or file is missing, then the backup has failed.
If it fails, just run the tool again a few times, or try rebooting your phone then rerun the tool. If you just can't get it to work, seek help from the tool thread.
Step 2 - Unlock the boot loader
Visit Sony's website and follow the instructions carefully
Important: Pay attention to the warnings. No, really, unlocking the boot loader will wipe your DRM keys (hence the need to back them up in Step 1) and trigger a factory reset, erasing everything on your phone.
After you've successfully unlocked the boot loader, unplug your phone and leave it powered off
Step 3 - Download stock firmware
Run XperiFirm, locate the correct Xperia Z5 Compact version of your phone (E5803/E5823) and download the firmware of your choice.
General recommendation is to download the "Customized" version that's available for your country.
Step 4 - Create a FTF file from the firmware
Open Flashtool
Tools > Bundle > Create
Select source file > Locate the folder where you saved the firmware from XperiFirm in step 3 > You should see your device name appear automatically in Device and the folder list below populated
Branding > The same as Operator in XperiFirm, e.g. Customized AU
Version > The version you downloaded, e.g. 32.2.A.5.11
Hint: Both Branding and Version information is in the folder name
In folder list, select the first item, hold SHIFT and select the last item so that all items are highlighted, then click the "- >" button > The folder list should now be empty, and the Firmware content field populated
Click Create, if successful you will see "Bundle creation finished"
Note: The FTF file is saved to %userprofile%\.flashTool\firmwares by default
Step 5 - Flash the FTF file
Click the lightning symbol in Flashtool > Flashmode
Source folder should be pre-selected to the default location mentioned above and "Sony Xperia Z5 Compact" listed in Firmwares
Expand all the arrows and select the version number
Under Wipe/Sin check all options (APPS_LOG, DIAG, SSD, USERDATA), leave all other options unchecked
Click Flash, wait for an instruction prompt to pop up
Plug the USB cable to your computer if it isn't already plugged
Turn off your phone if it isn't powered off, hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Flashtool will begin flashing the firmware automatically. It can take a long time, 10~15 minutes is normal, wait until completed
Unplug your phone and do not power it on yet
Step 6 - Patch the kernel
Download this awesome rootkernel tool, unzip to desired location.
Extract the kernel image file kernel.sin from the FTF file using any file compression program such as 7zip, WinZip, WinRAR, etc.
Open Flashtool > Tools > Sin Editor > Sin file > Locate the kernel you just extracted > Click Extract data. You should now have a file named kernel.elf in the same folder
Copy kernel.elf to the rootkernel folder
Download the latest stable version of the SuperSU ZIP file and copy the entire ZIP file to the rootkernel folder. Do NOT unzip it!
Rename the SuperSU ZIP file name so that it starts with SuperSU (case sensitive) instead of UPDATE-SuperSU, e.g. SuperSU-v2.79-20161211114519.zip
Note: if you're patching Nougat firmware, you may want to use phh's superuser instead of SuperSU due to potential battery drain. See rootkernel thread for more info. If you use phh's superuser, you will need to install the apk from the Play store after Step 8.
(optional) Download the latest Xposed framework ZIP file and copy it to the rootkernel folder. Do NOT unzip it!
Note: this only works with rootkernel v5.0 or later, if you're using an earlier version of the rootkernel tool, skip this and skip Step 9
At time of this edit (2017/2/22), Xposed does not support Android 7.0 (Nougat), so if you're trying to patch a Nougat kernel, do not include xposed. You can check the official Xposed thread for latest announcements to see if it's supported
Open command prompt and navigate to the rootkernel directory
Enter the following command:
Code:
rootkernel kernel.elf boot.img
You will be prompted to make a series of choices, including whether you want to install SuperSU and Xposed. Type Y for all of them.
If you didn't see the prompt for SuperSU (required) or Xposed (optional), check the filename of the ZIP files. Remember they're case sensitive.
You should now have a boot.img file in the rootkernel folder, that is your rooted kernel
Step 7 - Flash the DRM keys (one-time procedure)
tobias.waldvogel (rootkernel developer) said:
Flashing this file with flashtool will write your device key to an alternative unit, from where the drmfix library will pick it up.
This is a one-time task. It will survive a complete reset of the phone or Android system upgrade.
Click to expand...
Click to collapse
Copy the TA backup file TA_E5823.img from Step 1 to the rootkernel folder, then enter the following command in command prompt:
Code:
flash_dk TA_E5823.img DK.ftf
This will create a DK.ftf file in the rootkernel folder
Open Flashtool > Click the lightning symbol > Flashmode > Source folder > Locate the rootkernel folder
"Sony Xperia Z5 Compact" should appear under Firmwares, expand the arrows until you see DeviceKey and 1.0. Select 1.0, click Flash and wait for an instruction prompt to pop up
Hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Wait until operation is completed, then unplug the cable from your phone. Do not power on yet
Step 8 - Flash the kernel
Hold the VOLUME UP button and plug in the micro USB cable. Wait until the LED indicator turns blue, then release the VOL UP button.
Enter the following command in command prompt to flash the rooted kernel:
Code:
fastboot flash boot boot.img
After completion, congratulations, you've successfully rooted your phone!
Now you can turn on your phone, the first boot will take a very long time to initialize, don't worry.
If you see the boot animation for more than 30 minutes, then it's time to worry. First try again from Step 6, and if you still can't complete boot, go up a step starting from Step 5. If that still fails, start over from Step 3.
Step 9 - Finish installation of Xposed (optional)
In Step 6, if you chose to include the Xposed ZIP file, which means you want to install Xposed, then there's one more step to complete the installation.
Download the unofficial Material Design Xposed Installer.
Currently, this is the only Xposed Installer that works with the systemless Xposed integration method used by the rootkernel tool. Using the official Xposed Installer will not work.
Go to Settings > Security > Unknown sources > Toggle ON
Copy the Xposed Installer apk to your phone and install it.
Done!
Personal list of xposed modules to install for self reference. This is in no way a recommendation list, your preferences will vary.
Amplify
Android Phone Vibrator
App Locale
BootManager
Disable Low Battery Notifications
DynamicAlarmIcon 2
HideBatteryLowAlert
Keep Trash (broken at the moment)
Lockscreen Album Art Remover
MinMinGuard
NeoPowerMenu
NoHeadsetNotification
Ringer and Notification Volume Unlink
RootCloak
Use USB for Marshmallow V 1.2
XperiaFMwoHS
Xposed Torch: Physical keys
Youtube AdAway
Bonus - How to unroot/fully restore DRM/return to 100% factory state
Thank you for taking the time to write this guide!
best guide for root, thanks!
Fantastic guide, Thank you very much for that!
I had trouble getting the latest version of flashtool (09231) to work (mac and PC). It froze when I was trying to create the new bundle.
After downloading the older version (09186) it worked without problems.
However, currently I am stuck at step 6, running cmd 'rootkernel kernel.elf boot.img':
I get the message:
Code:
Rootkernel V5.11
- Unpacking kernel
error: Android boot magic not found
Unknown boot image format
Aborting
UPDATE:
I found the reason for the img file creation failure.
I was not patient enough in copying the kernel.elf file over. While the flashtool says file with size X created it was still compiling and only a minute later or so finished writing the file. In other words, I copied over the 'unfinished' kernel.elf and that's what caused the issue.
Trying to boot now
Thanks again for this nice guide!
Cheers,
Malcolm
Hey Malcolm, did you manage to complete the process successfully?
good news
thanks for your help. very good tutorial, realy made easy to understand
successfully rooted my nougat z5c with this,
you the best thanks
brokich said:
Hey Malcolm, did you manage to complete the process successfully?
Click to expand...
Click to collapse
Hi Brokich,
Unfortunately not (yet).
After finishing step 7 my device is stuck at the bootloader
I've tried now several times re-flashing (steps 5-7) but unfortunately no luck yet...Will try to repeat the whole procedure over the next days again.
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Hello guys
On step 5 i get this error
5/031/2017 13:31:03 - INFO - Device connected in flash mode
05/031/2017 13:31:28 - INFO - Selected Bundle for Sony Xperia Z5 Compact(E5823). FW release : 1298-5497_32.2.A.5.11_R13C. Customization : Customized UK
05/031/2017 13:31:28 - INFO - Preparing files for flashing
05/033/2017 13:33:12 - INFO - Please connect your device into flashmode.
05/033/2017 13:33:13 - INFO - Opening device for R/W
05/033/2017 13:33:14 - INFO - Start Flashing
05/033/2017 13:33:14 - INFO - Processing loader.sin
05/033/2017 13:33:14 - INFO - Checking header
05/033/2017 13:33:14 - ERROR - Processing of loader.sin finished with errors.
05/033/2017 13:33:14 - INFO - Ending flash session
05/033/2017 13:33:14 - ERROR - null
05/033/2017 13:33:14 - ERROR - Error flashing. Aborted
05/033/2017 13:33:14 - INFO - Device connected in flash mode
Any idea why ?
notabene said:
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Click to expand...
Click to collapse
Did you backup your TA-partition before the bootloader status was unknown?
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
Yes, why?
---------- Post added at 01:13 PM ---------- Previous post was at 12:49 PM ----------
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
I was able to flash FTF file. But not the kernel.
notabene said:
yes.
Click to expand...
Click to collapse
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
zegovernator said:
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
Click to expand...
Click to collapse
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Bootloader unlock allowed : yes
Remote Lock state : UnLockd
Checked DRM all OK
notabene said:
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Click to expand...
Click to collapse
Flash a .tft from the MM version your backed up your TA image from. When flashing, ensure to tick everything under wipe except TA Misc.
Well finally was able to do all the steps, but phone wont boot. Stucked in Sony logo, led is yellow and then power off..
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Need to use phone tomorrow, how can i revert to stock for a while since I cannot do it throught Xperia companion?
---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------
Malcolm143 said:
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Click to expand...
Click to collapse
Did you use customized firmware? I did not, i used Tmobile CZ
Now with bootloader unlocked even PC Companion doesnt work..
So the problem is after flashing custom kernel with rootkernel+DRM fix.
So after hours of trying from step 5 with different settings for kernel, I ended up with stock rom flashed via flashtool..
tried to flash back DRM keys from Dirty cow TA Backup, using this command flash_dk TA_E5823.img DK.ftf but when rebooted in service menu drm keys are still gone..
EDIT:
Seems like there is more users with same issue with Z5C and latest rootkernel
https://forum.xda-developers.com/xp...matic-repack-stock-kernel-dm-t3301605/page200
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
mhaha said:
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
Click to expand...
Click to collapse
Thanks, will try in the evening.
Just to know, if I'm upgrading from previous firmware version, do I have to do all steps or I can start from step 4 (flashing ftf file)?
I've got 2 things i want to adress, first of all my headunit occasionally boots up 2times (75% of the time), I will try a factory reset to see if that fixes it
secondly i want to be able to change bootanimation of my device, described below is my method but if i'm correct i will need to root my device to make it work), is this approach/method correct?
Change bootanimation OREO 8.1.0:
preparation
- Enable "read/write/execute" rights on the sdcard(android rootfolder) and allow file browser app root acces(fe: ES or FX explorer):
1. Enable USB debugging and (not applicable on headunits) OEM unlock in developper options
2. on pc Install android tools(adb) + android pc drivers, android device/emulator should be recognized in the devices list of my computer
3. connect pc to android headunit with USB (or wifi if using adb over wifi)
/* !Make a backup first from recovery mode or bootloader mode */
4. On PC, go to the android tools (where adb.exe is located), open a cmd prompt(Shift + right click)
in the cmd prompt:
4.1 adb devices - device should be listed here
4.2 adb reboot recovery - should reboot all connected devices into recovery mode, make a backup from the system and apps here, upon completion and in preparation of a factory reset: clear cache memory and app data/memory, upon completion, do a factory reset.
5 test. edit read/write/execute permissions(will probably be a no) and double boot "bug"
Actually change the bootanimation (with the headunit itself, using ES/FX file explorer):
1. place the downloaded bootanimation zip file to the sdcard, either "sdcard", "sdcard\system" or "sdcard\system\media"
2. change permission of the zip file to 644(read/write/execute)
3. open the stock "Bootanimation" app and select the newly added zip
4. reboot to test
If this doesnt work, my headunit needs to be rooted?:
I looked at numerous video's and tutorials to root a device(offcourse all diffrent devices and android versions) and i have some questions now.
For a car headunit, how do i know what files i need and what should i pay attention to, i have a china model(seicane) that uses an alwinner T8 processor, i have an android version(oreo 8.1.0), MCU version and a system version (not sure what this is). can i install custom recovery and any android version i want on this headunit, will it be compatible or how can i find out wether its compatible or not.
There are so few tutorials on how to root an android oreo headunit and i'm not sure the one(s) that is availlable will work for my device
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
ISSUE: FASTBOOT Might not work on windows 10 version 2004, a solution is to use a Linux virtual machine to use fastboot commands. Test it out first as you might be lucky and it could work for you.
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port, as USB 3.0 might give you issues with the fastboot commands)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Usyless said:
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Click to expand...
Click to collapse
Thank you excellent post just what I needed.
eedwin101 said:
Thank you excellent post just what I needed.
Click to expand...
Click to collapse
I'm glad it helped you
Usyless said:
I'm glad it helped you
Click to expand...
Click to collapse
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
eedwin101 said:
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
Click to expand...
Click to collapse
I know that phhussons AOSP works on this phone with no issues aswell, you might have to use securize to get safety net to pass tho.
android 11 will boot on this phone however iirc you won't be able to hear and other people won't hear you in phone calls.
havoc gsis I believe works but I haven't tested it and I have only heard of one person using it.
BLISS/LOSQ/CAOS don't work on this phone at all.
and after that I don't think there really is many more GSIs that work as they just won't boot for bizarre reasons
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
_Sherrif said:
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
Click to expand...
Click to collapse
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Usyless said:
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Click to expand...
Click to collapse
No AT&T.
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
or you could try this: https://t.me/razer_phone/12949
install instructions shown in the message
Usyless said:
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
Click to expand...
Click to collapse
Aight! Definitely worth a try. Tried everything else.
Thank you!
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
frannet said:
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
Click to expand...
Click to collapse
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Usyless said:
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Click to expand...
Click to collapse
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
frannet said:
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
Click to expand...
Click to collapse
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Usyless said:
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Click to expand...
Click to collapse
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
frannet said:
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
Click to expand...
Click to collapse
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Usyless said:
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Click to expand...
Click to collapse
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ??
frannet said:
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ?
Click to expand...
Click to collapse
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
i
Usyless said:
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
Click to expand...
Click to collapse
Hahaha, yeah, If I'm honest, dark mode in iOS work fine, very fine, normally I use my iPhone 11 and I play with android devices for.. for play with the OS and develoment OS, and as second andriods phone for maybe.... I go to check the gsi mode, thanks guy!!