> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Sony Xperia Z - Official firmware



Rep: (937)
Sony Xperia Z - Official firmware
PictureYuga, c6606, c6602, c6603, L36a, L36h, L36i
Description | Discussion | Purchase | Accessories | Marriage and Repair | Sony Xperia Z Owners Club | Sony & SE Owners Club | Modifications and decorations | Modems and communication | Custom firmware | CyanogenMod Firmware (OS 4.xx) | CyanogenMod 12 (OS 5.0.X) LOLLIPOP | MIUI firmware (OS 4.xx) | OmniROM Firmware (OS 4.x.x) | Official firmware (OS 4.xx)

Important information
Drivers and Utilities
Most stable drivers for Windows 8.1
Official
Unofficial
Official firmware
C6603

C6602
Core
Instructions
ROOT rights

About root-rights for Android 4.3
Route 4.3 is finally available in this manner . Are there any other options:
e-ch! @ 12/30/2013, 12:25*
1 - There are firmware with root, official, are sewed through CWM, do not differ in any way from off. Because this is what they are, only repacked with root and recovery.
2 - Unzip the bootloader, install a custom kernel
3 - Unzip the bootloader, put the type of existential

4 - For those who feel like it,still have that option!


Recovery


Firmware

Useful
Survey Screenshots

Survey on 12/06/2015
Attached Image

Poll from 07/16/2015
Attached Image

Poll 11.03.2015
Attached Image

Survey on 09/23/2014
Attached Image

Poll 08.07.2014
Attached Image

Survey on 05/22/2014
Attached Image

Poll 03/03/2014
Attached Image

Survey on 02/15/2014
[
Attached Image
]

Survey on 11/29/2013
Attached Image



There is no curator in the subject. For questions about filling the caps, please contact the section moderators via the buttonPictureunder the messages to which you want to add links.

Post has been editedsnekt - 17.10.19, 12:45
Reason for editing: editing



Rep: (152)
Newest fleshtulom close loaderabsolutely not !
One of the users in the HDA tried to lock, fastbut produced an error and is now in the service menu had an inscription Bootloader anlock allowed: Unknown. Developers have recognized that this is a bug and are working on this, and until told to fleshtulom bottles did not close one.



Rep: (1912)
DennisDD @ 11.03.2013, 07:45*
Newest fleshtulom close loader, you should not!

it is necessary to temporarily bring a hat, red, until corrected.



Rep: (1872)
Opel, it concerns bety2 that's just in the header is not present. The first beta, which is in the cap to close the boot loader can not.
I think just is not worth it to put in a cap betu2.



Rep: (414)
dogsly @ 11.03.2013, 04:20*
while it is not necessary to put a cap in betu2.

DennisDD @ 11.03.2013, 00:45*
Newest fleshtulom close loader, you should not!
So far, this beta will not be all clear in the header it will not be.



Rep: (1788)
DennisDD @ 11.03.2013, 00:45*
and now in the service menu had an inscription Bootloader anlock allowed: Unknown

And so what? The outcome of what? Kirpichnulsya chtol? Or what?



Rep: (152)
dantist_140 @ 11.03.2013, 19:47*
And so what? The outcome of what? Kirpichnulsya chtol? Or what?

Yes hell you know, try and then tell us how it :)



Rep: (414)
DennisDD @ 11.03.2013, 14:43*
try
So he Zetka no;)

Post has been editedVLADISLAV0711 - 11.03.13, 13:51



Rep: (1497)
Seem to be,found detourWho then can translate? : Smile:



Rep: (1788)
= AVS = @ 11.03.2013, 17:32*
someone can translate?

Right now we try. But in any case need a tester ... to more accurately describe the



Rep: (1497)
dantist_140 @ 11.03.2013, 17:36*
But in any case need a tester ... to more accurately describe the

I can participate

Archive itself ...
Attached fileEasyRootingToolkit_XPEIRAZ_SO-02E_v101.zip(1.92 MB)


Post has been edited= AVS = - 11.03.13, 16:41



Rep: (1788)
Root Xperia Z / ZL Locked bootloader / Preparation rue for blocked buta

Requirements
  • Timeout screen to switch to "10 minutes"
  • Enable "USB Debugging"
  • Allow "Unknown Sources"
  • Installed drivers for Fleshtula. (Flashtool - paragraph 3)

checked build

Instruction
  1. Unzip the contents of the zip
  2. Connect the phone to the PC.
  3. LaunchRunMe.bat and select the 3 points.
  4. On your phone, perform the Recover Data agrees to recovery.
    Attached Image

  5. At the command prompt appears on the implementation of the 1st stage, press, press any key to the next stage
  6. On your phone, Service window appears, select itService tests->Display
    Attached Image
    Attached Image

  7. The computer must continue with the installation, after vyponeniya any key, you can exit the program, and the phone will reboot. If nothing happens you need to complete the process computeradb.exe
  8. After rebooting, the phone icon will appear in the programsSuperuser

Getting Root:video 1 / video 2

Download

Source Goroh_kun / Source Bin4ry XDA

Post has been editeddantist_140 - 05.05.13, 18:21
Reason for editing: Updated script to v30



Rep: (1497)
dantist_140 @ 11.03.2013, 17:43*
In general, there is a horse-radish that can be understood by the description

One is not clear - it is necessary to drive it into fastbuta mode or what?



Rep: (1788)
= AVS = @ 11.03.2013, 17:49*
it is necessary to drive it into fastbuta mode or what?

No, as I understand it is something akin from Bin4ury. I will update the post as we go. Watch out.



Rep: (1497)
What a program to open the phone?

Damn ... this method as I understand it puts Root, root and rekoveri, bite ... that's just all in hieroglyphs} -)



Rep: (1788)
= AVS = @ 11.03.2013, 18:05*
What a program to open the phone?

This one;)
Attached Image
And what kind of prog - hell knows. I understand it's some sort of a program recovery or backup.
Or is it opens the batch file or set and it should be open. : Wacko:: huh:



Rep: (414)
dantist_140 @ 11.03.2013, 18:08*
And what kind of prog - hell knows.

On Google Translate, language detection;)



Rep: (1788)
VLADISLAV0711 @ 11.03.2013, 18:10*
On Google Translate, language detection

What resourceful ... try to translate myself a minute;)



Rep: (1497)
Something like thishttp://translate.google.ru/translate?hl=ru...rootingkit.html



Rep: (1788)
= AVS = @ 11.03.2013, 18:19*
Something like this

I yuzayu Google Chrome + auto-plugin from him.
So - no surprise;)
Nichrome is still not clear.

Basically I wrote, the rest of matter of practice. If anyone out, let them describe Che as I make a right.

Post has been editeddantist_140 - 11.03.13, 17:23



Rep: (1820)
dantist_140 @ 11.03.2013, 17:43*
Then I can not understand ((continue to dance

Here is the translation:
Translated version runme.txt
@echo off @ ECHO OFF
@echo ------------------------------------------------ ---------------------- @ Echo -------------------------- ---------------------- ----------------------
@echo Easy rooting Toolkit for XPEIRA Z SO-02E (ver 1.0.1) @ Echo Easy rooting toolkit for XPEIRA Z SO-02E (version 1.0.1)
@echo from @goroh_kun idea @ Echo of ideas @ goroh_kun
@echo by HUHKA (@huhka_com) @ Echo on HUHKA (@ huhka_com)
@echo ------------------------------------------------ ---------------------- @ Echo -------------------------- ---------------------- ----------------------
@echo [*] 実 行 内容: @ Echo, what to do [*]:
@echo (1) root 権 限 取得 @ Echo acquisition of office (1) Root
@echo (2) busybox イ ン ス ト ー ル @ Echo (2) BusyBox installed
@echo (3) su イ ン ス ト ー ル @ Echo (3) su installation
@echo (4) リ マ ウ ン ト 監視 の / sbin / ric 対 策 @ Echo monitoring (4) repair measures / sbin / RIC
@echo [*] 動作 確認 バ ー ジ ョ ン: @ Echo-tested version [*]:
@echo · 10.1.D.0.317 @ Echo · 10.1.D.0.317
@echo · 10.1.D.0.322 @ Echo · 10.1.D.0.322
@echo [*] 事前 準備: @ Echo training [*]:
@echo (1) USB ド ラ イ バ の イ ン ス ト ー ル @ Echo setup (1) USB Driver
@echo (2) 端末 側 「提供 元 不明 ア プ リ」 の 有効 化 @ Echo include "Unknown sources the application" Terminal side (2)
@echo (3) 端末 側 「USB デ バ ッ グ」 の 有効 化 @ ECHO Enable "USB Debugging" side of the terminal (3)
@echo (4) PC と 端末 の USB 接 続 USB connection and the terminal (4) PC @ Echo
@echo ------------------------------------------------ ---------------------- @ Echo -------------------------- ---------------------- ----------------------
pause pause
@if not exist. \ files \ adb.exe (goto FILE_FALSE_001) @ If you do not exist. \ Files \ adb.exe (go FILE_FALSE_001)
@if not exist. \ files \ AdbWinApi.dll (goto FILE_FALSE_002) @ If you do not exist. \ Files \ AdbWinApi.dll (go FILE_FALSE_002)
@if not exist. \ files \ AdbWinUsbApi.dll (goto FILE_FALSE_003) @ If you do not exist. \ Files \ AdbWinUsbApi.dll (go FILE_FALSE_003)
@if not exist. \ files \ busybox-armv6l (goto FILE_FALSE_004) @ If you do not exist. \ Files \ BusyBox-armv6l (go FILE_FALSE_004)
@if not exist. \ files \ install-recovery.sh (goto FILE_FALSE_005) @ If you do not exist. \ Files \ Install-recovery.sh (go FILE_FALSE_005)
@if not exist. \ files \ step2.sh (goto FILE_FALSE_006) @ If you do not exist. \ Files \ step2.sh (go FILE_FALSE_006)
@if not exist. \ files \ su (goto FILE_FALSE_007) @ If you do not exist. \ Files \ SU (go FILE_FALSE_007)
@if not exist. \ files \ Superuser.apk (goto FILE_FALSE_008) @ If you do not exist. \ Files \ Superuser.apk (go FILE_FALSE_008)
@if not exist. \ files \ onload.sh (goto FILE_FALSE_101) @ If you do not exist. \ Files \ onload.sh (go FILE_FALSE_101)
@if not exist. \ files \ step3.sh (goto FILE_FALSE_009) @ If you do not exist. \ Files \ step3.sh (go FILE_FALSE_009)

rem # goroh_kun files REM # goroh_kun files
@if not exist. \ z_rootkit \ getroot.sh (goto FILE_FALSE_101) @ If you do not exist. \ Z_rootkit \ getroot.sh (go FILE_FALSE_101)
@if not exist. \ z_rootkit \ usbux.ab (goto FILE_FALSE_101) @ If you do not exist. \ Z_rootkit \ usbux.ab (go FILE_FALSE_101)

goto FILE_TRUE On FILE_TRUE

: FILE_FALSE_001: FILE_FALSE_001
@echo Error! adb.exe が 有 り ま せ ん There is no mistake @ echo! Adb.exe
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_002: FILE_FALSE_002
@echo Error! AdbWinApi.dll が 有 り ま せ ん There is no mistake @ echo! AdbWinApi.dll
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_003: FILE_FALSE_003
@echo Error! AdbWinUsbApi.dll が 有 り ま せ ん There is no mistake @ echo! AdbWinUsbApi.dll
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_004: FILE_FALSE_004
@echo Error! busybox-armv6l が 有 り ま せ ん There is no mistake @ echo! Busybox-armv6l
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_005: FILE_FALSE_005
@echo Error! install-recovery.sh が 有 り ま せ ん There is no mistake @ echo! Install-recovery.sh
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_006: FILE_FALSE_006
@echo Error! step2.sh が 有 り ま せ ん There is no mistake @ echo! Step2.sh
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_007: FILE_FALSE_007
@echo Error! su が 有 り ま せ ん There is no mistake @ echo! sou
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_008: FILE_FALSE_008
@echo Error! Superuser.apk が 有 り ま せ ん There is no mistake @ echo! Superuser.apk
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_009: FILE_FALSE_009
@echo Error! step3.sh が 有 り ま せ ん There is no mistake @ echo! Step3.sh
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_101: FILE_FALSE_101
@echo Error! getroot.sh が 有 り ま せ ん There is no mistake @ echo! Getroot.sh
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_102: FILE_FALSE_102
@echo Error! onload.sh が 有 り ま せ ん There is no mistake @ echo! Onload.sh
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE_103: FILE_FALSE_103
@echo Error! usbux.ab が 有 り ま せ ん There is no mistake @ echo! Usbux.ab
goto FILE_FALSE On FILE_FALSE

: FILE_FALSE: FILE_FALSE
@echo 必要 な フ ァ イ ル が 無 い の で 実 行 で き ま せ ん I can not be performed because there is no necessary files @ Echo
pause pause
goto BATCH_END On BATCH_END

: FILE_TRUE: FILE_TRUE
@echo ### 処理 開始! The process begins echo @ # # #! ### # # #
@echo ADB で の 接 続 待 ち Waiting for connection on @ Echo ADB
@files \ adb wait-for-device @ Files \ ADB expectations for devices

@echo 必要 フ ァ イ ル を 端末 側 に 転 送 し ま す そ の 1 Part 1 should be transferred to the terminal side of the desired file @ Echo
@files \ adb push files \ onload.sh / data / local / tmp / @ Files \ files ADB push \ onload.sh / data / local / the TMP /
@files \ adb shell "chmod 755 /data/local/tmp/onload.sh" @ Files \ adb shell "CHMOD 755 / data / local / TMP / onload.sh"
@files \ adb push z_rootkit \ getroot.sh / data / local / tmp / @ Files \ ADB push z_rootkit \ getroot.sh / data / local / the TMP /
@files \ adb shell "chmod 755 /data/local/tmp/getroot.sh" @ Files \ adb shell "CHMOD 755 / data / local / TMP / getroot.sh"

@echo ------------------------------------------------ ---------------------- @ Echo -------------------------- ---------------------- ----------------------
@echo [*] 手 順 説明: Step-by-step instructions @ echo [*]:
@echo 1. 端末 操作 で デ ー タ の 復 元 ボ タ ン を 押 し て く だ さ い. Please click on the button to restore the terminal operation data 1. @ Echo.
@files \ adb restore z_rootkit \ usbux.ab @ Files \ ADB recovery z_rootkit \ usbux.ab
@echo デ ー タ の 復 元 が 完了 し た ら, @ Echo data recovery is complete,
@pause @ Pause

@echo ------------------------------------------------ ---------------------- @ Echo -------------------------- ---------------------- ----------------------
@echo [*] 手 順 説明: Step-by-step instructions @ echo [*]:
@echo 1. 端末 の 画面 か ら Service tests を 選 択 Select the service terminal screen tests 1. @ Echo
@echo 2. Display を 選 択 Select 2. Display @ Echo
@echo ※ 再 起動 完了 ま で 画面 が 真 っ 白 で す White screen complete restart @ echo ※
@files \ adb shell "am start -a android.intent.action.MAIN -n com.sonyericsson.android.servicemenu / .ServiceMainMenu" @ Files \ adb shell "morning run android.intent.action.MAIN-n com.sonyericsson .android.servicemenu /. ServiceMainMenu "
@echo 処理 中 /data/local/tmp/onload.sh ... / Data / local / TMP / onload.sh processed @ echo ...
@files \ adb shell "while:; do [-w / sys / kernel / uevent_helper] && exit; done" @ Files \ adb shell "and do :; [-W / system / kernel / uevent_helper] && exit; done "
@files \ adb shell "echo /data/local/tmp/getroot.sh>/ Sys / kernel / uevent_helper "@ Files \ adb shell" echo / data / local / TMP / getroot.sh>/ Sys / kernel / uevent_helper "

@echo ------------------------------------------------ ---------------------- @ Echo -------------------------- ---------------------- ----------------------
@echo [*] 手 順 説明: Step-by-step instructions @ echo [*]:
@echo 1. 電源 ボ タ ン で 画面 を 消 灯 さ せ る to turn off the screen using the power button 1. @ Echo
@echo 2. 電源 ボ タ ン で 画面 を 点灯 さ せ る to light up the screen using the power button 2. @ Echo
@echo ※ 場合 に よ っ て は 何 も し な い で も 通過 し ま す ♪ @ Echo ※ ♪ Sometimes I will also pass through without doing anything
@echo ------------------------------------------------ ---------------------- @ Echo -------------------------- ---------------------- ----------------------
@files \ adb shell "while:; do [-f / dev / sh] && exit; done" @ Files \ adb shell "and do :; [-F / Dev / w] && exit; done"

@echo 必要 フ ァ イ ル を 端末 側 に 転 送 し ま す そ の 2 Part 2 to be converted into the desired file @ echo terminal
@files \ adb push files \ busybox-armv6l / data / local / tmp / busybox @ Files \ files ADB push \ BusyBox-armv6l / data / local / TMP / BusyBox
@files \ adb push files \ install-recovery.sh / data / local / tmp / @ Files \ files ADB push \ Install-recovery.sh / data / local / the TMP /
@files \ adb push files \ step2.sh / data / local / tmp / @ Files \ files ADB push \ step2.sh / data / local / the TMP /
@files \ adb push files \ step3.sh / data / local / tmp / @ Files \ files ADB push \ step3.sh / data / local / the TMP /
@files \ adb push files \ su / data / local / tmp / @ Files \ ADB push files \ su / data / local / the TMP /
@files \ adb shell "chmod 777 /data/local/tmp/step2.sh" @ Files \ adb shell "CHMOD 777 / data / local / tmp / step2.sh"
@files \ adb shell "chmod 777 /data/local/tmp/step3.sh" @ Files \ adb shell "CHMOD 777 / data / local / tmp / step3.sh"

@echo busybox, su, Superuser 等 の イ ン ス ト ー ル ♪ ♪ @ echo Installing BusyBox, su, Superuser, etc.
@files \ adb shell "/ dev / sh /data/local/tmp/step2.sh" @ Files \ adb shell "/ Dev / w / data / local / tmp / step2.sh"
@files \ adb install files \ Superuser.apk @ Files \ ADB installation files \ Superuser.apk

: BATCH_PROC_POST: BATCH_PROC_POST
@echo 後 始末 @ ECHO cleaning
@files \ adb shell "/ dev / sh /data/local/tmp/step3.sh" @ Files \ adb shell "/ Dev / w / data / local / tmp / step3.sh"

: BATCH_PROC_POST_DELFILE02: BATCH_PROC_POST_DELFILE02
@files \ adb shell "rm / data / local / tmp / busybox" @ Files \ adb shell "RM / data / local / TMP / BusyBox"
@files \ adb shell "rm /data/local/tmp/install-recovery.sh" @ Files \ adb shell "RM / data / local / the TMP / installation-recovery.sh"
@files \ adb shell "rm /data/local/tmp/step2.sh" @ Files \ adb shell "RM / data / local / tmp / step2.sh"
@files \ adb shell "rm / data / local / tmp / su" @ Files \ adb shell "RM / data / local / the TMP / su"

: BATCH_PROC_POST_DELFILE01: BATCH_PROC_POST_DELFILE01
@files \ adb shell "rm /data/local/tmp/onload.sh" @ Files \ adb shell "RM / data / local / TMP / onload.sh"
@files \ adb shell "rm /data/local/tmp/getroot.sh" @ Files \ adb shell "RM / data / local / TMP / getroot.sh"

@echo 再 起動 し ま す @ Echo Reboot
@files \ adb reboot @ Files \ ADB reboot

@echo ADB で の 接 続 待 ち Waiting for connection on @ Echo ADB
@files \ adb wait-for-device @ Files \ ADB expectations for devices
@echo ### 処理 完了! Processing is completed @ ECHO # # #! ### # # #

: BATCH_END: ​​BATCH_END
pause pause


Full version    

Help     rules

Time is now: 21/05/20, 7:10