Recovery & Root for MM .575 & .291 LB

Search This thread

Antwanster

Member
Oct 18, 2013
17
3
Hello,

Im running .575 firmware, stock kernel, stock firmware, with TWRP AND Xposed framework. I lost my root when I updated from 5.x to 6.1.
When I run this phone reboots into recovery... but i don't have root.

Any suggestions?

EDIT: I noticed this:

Code:
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Device Detected!

Installing ...

[100%] /data/local/tmp/mm_twrp_recovery_install/boot_twrp_recovery.sh
[100%] /data/local/tmp/mm_twrp_recovery_install/busybox
[100%] /data/local/tmp/mm_twrp_recovery_install/byeselinux.ko
[100%] /data/local/tmp/mm_twrp_recovery_install/chargemon.sh
[100%] /data/local/tmp/mm_twrp_recovery_install/install_twrp_recovery.sh
[100%] /data/local/tmp/mm_twrp_recovery_install/iovyroot
[100%] /data/local/tmp/mm_twrp_recovery_install/modulecrcpatch
[100%] /data/local/tmp/mm_twrp_recovery_install/recovery.twrp.cpio.lzma
[100%] /data/local/tmp/mm_twrp_recovery_install/wp_mod.ko
iovyroot by zxz0O0
poc by idler1984


[+] Installing func ptr
    [+] Patching address 0xc1234b68
    [+] Start map/unmap thread
    [+] Start write thread
    [+] Spraying kernel heap
    [+] Start read thread
    [+] Done
got root lmao

"modulecrcpatch (by zxz0O0)
module_layout: patched to 0x2067C442
__aeabi_unwind_cpp_pr1: not found
kallsyms_lookup_name: not found
printk: match
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match

modulecrcpatch (by zxz0O0)

module_layout: not found
__aeabi_unwind_cpp_pr1: not found
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: not found

[U][B]...a whole lot more inbetween,  but I am removing it so the post doesn't become long.[/B][/U]

modulecrcpatch (by zxz0O0)

module_layout: not found
__aeabi_unwind_cpp_pr1: not found
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: not found


module_layout: not found
memcmp: not found
kallsyms_lookup_name: not found
__aeabi_unwind_cpp_pr0: not found
call_usermodehelper_exec: not found
call_usermodehelper_setfns: not found
call_usermodehelper_setup: not found
printk: not found
Installing of installbyeselinux.sh finished
Finished!"
 
Last edited:

casouzaj

Senior Member
Oct 13, 2006
2,236
576
57
Haibara-gum Yoshida-cho Sumiyoshi-shi
Hi, where ir Flash SU? ...
Copy the SuperSU zip to anywhere you want on your smartphone, on either the internal storage or the SD card. Once you have run the install.bat file on your PC, or pressed the volume down button at the moment the led flashed in green color, along with a vibration, right after the first Sony Xperia screen, in a reboot operation, you got under TWRP. There, tap on Install, navigate to where you placed the SuperSU zip, tap over it and slide the bottom bar to the right to get the installation executed.

I recommend not to install the SR1 version of SuperSU. It doesn't fit right on our devices. I suggest the v2.78 one tagged as SYSTEMMODE.
 

dawenz824

Member
May 7, 2015
10
0
Help

Copy the SuperSU zip to anywhere you want on your smartphone, on either the internal storage or the SD card. Once you have run the install.bat file on your PC, or pressed the volume down button at the moment the led flashed in green color, along with a vibration, right after the first Sony Xperia screen, in a reboot operation, you got under TWRP. There, tap on Install, navigate to where you placed the SuperSU zip, tap over it and slide the bottom bar to the right to get the installation executed.

I recommend not to install the SR1 version of SuperSU. It doesn't fit right on our devices. I suggest the v2.78 one tagged as SYSTEMMODE.

Hi doc, i will try to generate mi own tft, because my phone is locked ... how i can get it.. I dont know waht i have to put in Branding and Version in FlashTools... :/
 

Peloche

Member
Jan 24, 2015
5
0
Hello,

Im running .575 firmware, stock kernel, stock firmware, with TWRP AND Xposed framework. I lost my root when I updated from 5.x to 6.1.
When I run this phone reboots into recovery... but i don't have root.

Any suggestions?

EDIT: I noticed this:

Code:
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Device Detected!

Installing ...

[100%] /data/local/tmp/mm_twrp_recovery_install/boot_twrp_recovery.sh
[100%] /data/local/tmp/mm_twrp_recovery_install/busybox
[100%] /data/local/tmp/mm_twrp_recovery_install/byeselinux.ko
[100%] /data/local/tmp/mm_twrp_recovery_install/chargemon.sh
[100%] /data/local/tmp/mm_twrp_recovery_install/install_twrp_recovery.sh
[100%] /data/local/tmp/mm_twrp_recovery_install/iovyroot
[100%] /data/local/tmp/mm_twrp_recovery_install/modulecrcpatch
[100%] /data/local/tmp/mm_twrp_recovery_install/recovery.twrp.cpio.lzma
[100%] /data/local/tmp/mm_twrp_recovery_install/wp_mod.ko
iovyroot by zxz0O0
poc by idler1984


[+] Installing func ptr
    [+] Patching address 0xc1234b68
    [+] Start map/unmap thread
    [+] Start write thread
    [+] Spraying kernel heap
    [+] Start read thread
    [+] Done
got root lmao

"modulecrcpatch (by zxz0O0)
module_layout: patched to 0x2067C442
__aeabi_unwind_cpp_pr1: not found
kallsyms_lookup_name: not found
printk: match
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match

modulecrcpatch (by zxz0O0)

module_layout: not found
__aeabi_unwind_cpp_pr1: not found
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: not found

[U][B]...a whole lot more inbetween,  but I am removing it so the post doesn't become long.[/B][/U]

modulecrcpatch (by zxz0O0)

module_layout: not found
__aeabi_unwind_cpp_pr1: not found
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: not found


module_layout: not found
memcmp: not found
kallsyms_lookup_name: not found
__aeabi_unwind_cpp_pr0: not found
call_usermodehelper_exec: not found
call_usermodehelper_setfns: not found
call_usermodehelper_setup: not found
printk: not found
Installing of installbyeselinux.sh finished
Finished!"

I have the same problem on 291 fw and 575 kernel. Please help me
 

casouzaj

Senior Member
Oct 13, 2006
2,236
576
57
Haibara-gum Yoshida-cho Sumiyoshi-shi
Seriously? I thought that wasn't possible!

There's not even a chance of that happening? Can I back them up? If the answer is yes, how could I do that?

Does this method prevent me from updating, assuming Sony will release any more patches, that is.
You don't have to worry about your DRM keys. They will not be touched, at all, by this method.

Well, once rooted, all OTA updates will fail to be installed. It's not a real problem, though. Flashtool is here to help us, and it's a very powerful tool.
 

russel5

Senior Member
Jun 13, 2012
813
1,217
38
Yekaterinburg
Hello,
Im running .575 firmware, stock kernel, stock firmware, with TWRP AND Xposed framework. I lost my root when I updated from 5.x to 6.1.
When I run this phone reboots into recovery... but i don't have root.
Any suggestions?
I have the same problem on 291 fw and 575 kernel. Please help me

Yes, please guys learn2read what i wrote in first post:
Code:
[B][COLOR="Red"]Then you can install any supersu.zip in custom recovery[/COLOR][/B]
 
  • Like
Reactions: shoey63 and yo7fb

Macsek

Senior Member
Apr 29, 2007
85
24
Budapest
installing from linux

Hi folks,

I modified the windows-only method to run under linux, created install.sh (had to compress it to upload in xda, run gunzip install.sh.gz to extract).
@russel5, can you please insert a link to this post in the 1st post, others can find it useful too.

"Thanks! :good:" button is for free ;)
 

Attachments

  • install.sh.gz
    386 bytes · Views: 1,563

ihko

New member
Nov 7, 2016
4
0
Hello all

First, sorry for my basic english :)
I'm desperatly trying to root my Z3C...And i'm stucked on 1st step...(It's my first attempt to root a phone :) )

Actual phone information : Android version : 6.0.1 / kernel version : 3.4.0-perf-g43ea728 / Build number : 23.5.A.1.291 (according to flashtool)
So I downloaded zip files, renamed them, and trying to flash 291 to 575. 6th times today but without success...

I saved the flashtool log and joined it. Can someone can tell me what I'm doing wrong please :crying: ?

07/002/2016 22:02:28 - INFO - Device connected with USB debugging on
07/002/2016 22:02:28 - INFO - Connected device : Sony Xperia Z3 Compact
07/002/2016 22:02:28 - INFO - Installed version of busybox : N/A
07/002/2016 22:02:28 - INFO - Android version : 6.0.1 / kernel version : 3.4.0-perf-g43ea728 / Build number : 23.5.A.1.291
07/002/2016 22:02:28 - INFO - Root access denied
07/002/2016 22:02:51 - INFO - Selected Bundle for Sony Xperia Z3 Compact(D5803). FW release : 23.5.A.0.575_R3D. Customization : stock kernel
07/002/2016 22:02:51 - INFO - Preparing files for flashing
07/002/2016 22:02:52 - INFO - Please connect your device into flashmode.
07/002/2016 22:02:56 - INFO - Device disconnected
07/003/2016 22:03:19 - INFO - Device connected in flash mode
07/003/2016 22:03:19 - INFO - Opening device for R/W
07/003/2016 22:03:19 - INFO - Reading device information
07/003/2016 22:03:19 - INFO - Phone ready for flashmode operations.
07/003/2016 22:03:19 - INFO - Opening TA partition 2
07/003/2016 22:03:19 - INFO - Current device : D5803 - YT911AP17M - 1288-7915_R2D - 1285-6521_23.5.A.0.575 - GLOBAL-LTE_23.5.A.1.291
07/003/2016 22:03:19 - INFO - Closing TA partition
07/003/2016 22:03:19 - INFO - Start Flashing
07/003/2016 22:03:19 - INFO - Processing loader.sin
07/003/2016 22:03:19 - INFO - Checking header
07/003/2016 22:03:19 - INFO - Flashing data
07/003/2016 22:03:20 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_M_2 / Bootloader status : ROOTABLE
07/003/2016 22:03:20 - INFO - Max packet size set to 512K
07/003/2016 22:03:20 - INFO - USB buffer size set to 512K
07/003/2016 22:03:20 - INFO - Parsing boot delivery
07/003/2016 22:03:31 - INFO - Found a template session. Using it : C:\Users\Thomas\.flashTool\devices\D58XX\default.fsc
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Writing TA unit 00002774. Value : 01
07/003/2016 22:03:31 - INFO - Closing TA partition
07/003/2016 22:03:31 - WARN - partition is excluded from bundle
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Closing TA partition
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Writing TA unit 0000084F. Value : 1A CE 28 00 01 00 06 05 00 02 02 08 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 05 00 05 83 02 00 10 02 00 05 85 12 00 02 00 A9 09 BE BA A9 09 00 00 B3 08 BE BA B3 08 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01 03 00 09 00 01
07/003/2016 22:03:31 - INFO - Writing TA unit 000008FD. Value : 00
07/003/2016 22:03:31 - INFO - Closing TA partition
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Processing dbi_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:31 - INFO - Checking header
07/003/2016 22:03:31 - INFO - Flashing data
07/003/2016 22:03:31 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:31 - INFO - Checking header
07/003/2016 22:03:31 - INFO - Flashing data
07/003/2016 22:03:31 - INFO - Processing rpm_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:31 - INFO - Checking header
07/003/2016 22:03:31 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Processing s1sbl_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Processing sbl1_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Processing tz_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Closing TA partition
07/003/2016 22:03:32 - INFO - Opening TA partition 2
07/003/2016 22:03:32 - WARN - cache is excluded from bundle
07/003/2016 22:03:32 - WARN - apps_log is excluded from bundle
07/003/2016 22:03:32 - INFO - Processing kernel.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:34 - WARN - fotakernel is excluded from bundle
07/003/2016 22:03:34 - INFO - Closing TA partition
07/003/2016 22:03:34 - INFO - Opening TA partition 2
07/003/2016 22:03:34 - WARN - userdata is excluded from bundle
07/003/2016 22:03:34 - WARN - system is excluded from bundle
07/003/2016 22:03:34 - WARN - amss_fs_1 is excluded from bundle
07/003/2016 22:03:34 - WARN - amss_fs_2 is excluded from bundle
07/003/2016 22:03:34 - WARN - amss_fsg is excluded from bundle
07/003/2016 22:03:34 - INFO - Closing TA partition
07/003/2016 22:03:34 - INFO - Opening TA partition 2
07/003/2016 22:03:34 - WARN - Unit 2212 not found in bundle
07/003/2016 22:03:34 - INFO - Closing TA partition
07/003/2016 22:03:34 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - WARN - Unit 2404 not found in bundle
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - WARN - elabel is excluded from bundle
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - INFO - Writing TA unit 00002725. Value : 32 30 31 36 2D 31 31 2D 30 37 20 32 32 3A 30 33 3A 33 35 00
07/003/2016 22:03:35 - INFO - Writing TA unit 00002774. Value : 00
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Ending flash session
07/003/2016 22:03:35 - INFO - Flashing finished.
07/003/2016 22:03:35 - INFO - Please unplug and start your phone
PHP:

Sorry for the long log :/
 

casouzaj

Senior Member
Oct 13, 2006
2,236
576
57
Haibara-gum Yoshida-cho Sumiyoshi-shi
Hello all

First, sorry for my basic english :)
I'm desperatly trying to root my Z3C...And i'm stucked on 1st step...(It's my first attempt to root a phone :) )

Actual phone information : Android version : 6.0.1 / kernel version : 3.4.0-perf-g43ea728 / Build number : 23.5.A.1.291 (according to flashtool)
So I downloaded zip files, renamed them, and trying to flash 291 to 575. 6th times today but without success...

I saved the flashtool log and joined it. Can someone can tell me what I'm doing wrong please :crying: ?

07/002/2016 22:02:28 - INFO - Device connected with USB debugging on
07/002/2016 22:02:28 - INFO - Connected device : Sony Xperia Z3 Compact
07/002/2016 22:02:28 - INFO - Installed version of busybox : N/A
07/002/2016 22:02:28 - INFO - Android version : 6.0.1 / kernel version : 3.4.0-perf-g43ea728 / Build number : 23.5.A.1.291
07/002/2016 22:02:28 - INFO - Root access denied
07/002/2016 22:02:51 - INFO - Selected Bundle for Sony Xperia Z3 Compact(D5803). FW release : 23.5.A.0.575_R3D. Customization : stock kernel
07/002/2016 22:02:51 - INFO - Preparing files for flashing
07/002/2016 22:02:52 - INFO - Please connect your device into flashmode.
07/002/2016 22:02:56 - INFO - Device disconnected
07/003/2016 22:03:19 - INFO - Device connected in flash mode
07/003/2016 22:03:19 - INFO - Opening device for R/W
07/003/2016 22:03:19 - INFO - Reading device information
07/003/2016 22:03:19 - INFO - Phone ready for flashmode operations.
07/003/2016 22:03:19 - INFO - Opening TA partition 2
07/003/2016 22:03:19 - INFO - Current device : D5803 - YT911AP17M - 1288-7915_R2D - 1285-6521_23.5.A.0.575 - GLOBAL-LTE_23.5.A.1.291
07/003/2016 22:03:19 - INFO - Closing TA partition
07/003/2016 22:03:19 - INFO - Start Flashing
07/003/2016 22:03:19 - INFO - Processing loader.sin
07/003/2016 22:03:19 - INFO - Checking header
07/003/2016 22:03:19 - INFO - Flashing data
07/003/2016 22:03:20 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_M_2 / Bootloader status : ROOTABLE
07/003/2016 22:03:20 - INFO - Max packet size set to 512K
07/003/2016 22:03:20 - INFO - USB buffer size set to 512K
07/003/2016 22:03:20 - INFO - Parsing boot delivery
07/003/2016 22:03:31 - INFO - Found a template session. Using it : C:\Users\Thomas\.flashTool\devices\D58XX\default.fsc
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Writing TA unit 00002774. Value : 01
07/003/2016 22:03:31 - INFO - Closing TA partition
07/003/2016 22:03:31 - WARN - partition is excluded from bundle
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Closing TA partition
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Writing TA unit 0000084F. Value : 1A CE 28 00 01 00 06 05 00 02 02 08 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 05 00 05 83 02 00 10 02 00 05 85 12 00 02 00 A9 09 BE BA A9 09 00 00 B3 08 BE BA B3 08 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01 03 00 09 00 01
07/003/2016 22:03:31 - INFO - Writing TA unit 000008FD. Value : 00
07/003/2016 22:03:31 - INFO - Closing TA partition
07/003/2016 22:03:31 - INFO - Opening TA partition 2
07/003/2016 22:03:31 - INFO - Processing dbi_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:31 - INFO - Checking header
07/003/2016 22:03:31 - INFO - Flashing data
07/003/2016 22:03:31 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:31 - INFO - Checking header
07/003/2016 22:03:31 - INFO - Flashing data
07/003/2016 22:03:31 - INFO - Processing rpm_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:31 - INFO - Checking header
07/003/2016 22:03:31 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Processing s1sbl_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Processing sbl1_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Processing tz_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:32 - INFO - Closing TA partition
07/003/2016 22:03:32 - INFO - Opening TA partition 2
07/003/2016 22:03:32 - WARN - cache is excluded from bundle
07/003/2016 22:03:32 - WARN - apps_log is excluded from bundle
07/003/2016 22:03:32 - INFO - Processing kernel.sin
07/003/2016 22:03:32 - INFO - Checking header
07/003/2016 22:03:32 - INFO - Flashing data
07/003/2016 22:03:34 - WARN - fotakernel is excluded from bundle
07/003/2016 22:03:34 - INFO - Closing TA partition
07/003/2016 22:03:34 - INFO - Opening TA partition 2
07/003/2016 22:03:34 - WARN - userdata is excluded from bundle
07/003/2016 22:03:34 - WARN - system is excluded from bundle
07/003/2016 22:03:34 - WARN - amss_fs_1 is excluded from bundle
07/003/2016 22:03:34 - WARN - amss_fs_2 is excluded from bundle
07/003/2016 22:03:34 - WARN - amss_fsg is excluded from bundle
07/003/2016 22:03:34 - INFO - Closing TA partition
07/003/2016 22:03:34 - INFO - Opening TA partition 2
07/003/2016 22:03:34 - WARN - Unit 2212 not found in bundle
07/003/2016 22:03:34 - INFO - Closing TA partition
07/003/2016 22:03:34 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - WARN - Unit 2404 not found in bundle
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - WARN - elabel is excluded from bundle
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Opening TA partition 2
07/003/2016 22:03:35 - INFO - Writing TA unit 00002725. Value : 32 30 31 36 2D 31 31 2D 30 37 20 32 32 3A 30 33 3A 33 35 00
07/003/2016 22:03:35 - INFO - Writing TA unit 00002774. Value : 00
07/003/2016 22:03:35 - INFO - Closing TA partition
07/003/2016 22:03:35 - INFO - Ending flash session
07/003/2016 22:03:35 - INFO - Flashing finished.
07/003/2016 22:03:35 - INFO - Please unplug and start your phone
PHP:

Sorry for the long log :/
Take a look at the kernel build date, under Settings > About phone. If it's dated April 22, 2016, it's from the 575 firmware, and you're ready to run the rooting tool. Otherwise, if it's June 28, 2016, instead, try to repeat the 575 kernel flashing operation, but, this time, reject the FSC file usage (I.e. answer NO to that question).
 
Last edited:

ihko

New member
Nov 7, 2016
4
0
It's written

3.4.0-per-g43ea728
[email protected]#1
Fri Apr 22 17:27:56 2016

I try the next step.

Thanks ;)

---------- Post added at 10:59 PM ---------- Previous post was at 10:47 PM ----------

I think it worked

07/056/2016 22:56:50 - INFO - Starting phone detection
07/056/2016 22:56:54 - INFO - Device connected with USB debugging on
07/056/2016 22:56:55 - INFO - Connected device : Sony Xperia Z3 Compact
07/056/2016 22:56:55 - INFO - Installed version of busybox : BusyBox v1.24.2 (2016-09-06 23:58:53 YEKT) multi-call binary.
07/056/2016 22:56:55 - INFO - Android version : 6.0.1 / kernel version : 3.4.0-perf-g43ea728 / Build number : 23.5.A.1.291
07/056/2016 22:56:55 - INFO - Checking root access
07/057/2016 22:57:03 - INFO - Installing toolbox to device...
07/057/2016 22:57:03 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
07/057/2016 22:57:03 - INFO - Running installftkit as root thru sysrun
07/057/2016 22:57:04 - INFO - Root Access Allowed
07/057/2016 22:57:04 - INFO - Stopping ric service
07/057/2016 22:57:04 - INFO - ric service stopped successfully

:)

Do I have to run the flashtool to kernel 291 ? Or It's Ok?
 

casouzaj

Senior Member
Oct 13, 2006
2,236
576
57
Haibara-gum Yoshida-cho Sumiyoshi-shi
It's written

3.4.0-per-g43ea728
[email protected]#1
Fri Apr 22 17:27:56 2016

I try the next step.

Thanks ;)

---------- Post added at 10:59 PM ---------- Previous post was at 10:47 PM ----------

I think it worked

07/056/2016 22:56:50 - INFO - Starting phone detection
07/056/2016 22:56:54 - INFO - Device connected with USB debugging on
07/056/2016 22:56:55 - INFO - Connected device : Sony Xperia Z3 Compact
07/056/2016 22:56:55 - INFO - Installed version of busybox : BusyBox v1.24.2 (2016-09-06 23:58:53 YEKT) multi-call binary.
07/056/2016 22:56:55 - INFO - Android version : 6.0.1 / kernel version : 3.4.0-perf-g43ea728 / Build number : 23.5.A.1.291
07/056/2016 22:56:55 - INFO - Checking root access
07/057/2016 22:57:03 - INFO - Installing toolbox to device...
07/057/2016 22:57:03 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
07/057/2016 22:57:03 - INFO - Running installftkit as root thru sysrun
07/057/2016 22:57:04 - INFO - Root Access Allowed
07/057/2016 22:57:04 - INFO - Stopping ric service
07/057/2016 22:57:04 - INFO - ric service stopped successfully

:)

Do I have to run the flashtool to kernel 291 ? Or It's Ok?
Has your phone entered TWRP at the end of the process? If so, have you installed the SuperSU zip whilst still under the TWRP session? Yes, it's highly recommended to flash the 291 kernel back as the last operation, in order to avoid a persistent upgrade notification in your status bar.
 
  • Like
Reactions: ihko

ihko

New member
Nov 7, 2016
4
0
Has your phone entered TWRP at the end of the process? If so, have you installed the SuperSU zip whilst still under the TWRP session? Yes, it's highly recommended to flash the 291 kernel back as the last operation, in order to avoid a persistent upgrade notification in your status bar.

Yes there was a weird screen with strange tiles, I supposed it was TWRP (I don't know what it exactly is lol). Still, I checked other post in the thread and downloaded the latest version of SuperSu on my PC, copy/paste the Zip with WinExplorer to SD Card and installed it through the supposed TWRP. And it worked :good:

Now I have to flash the 291 kernel back.

Thank's again :)
 

MisterVolum

Member
Oct 10, 2012
8
2
if you ”Run as administrator” the install.bat but keep getting the error: adb server version (32) doesn't match this client (36) Killing.... be sure to firstly kill the process Xperia Companion (or something like this) from Task Manager. Then run again as administrator the install.bat and now it should work.
I struggled several hours trying to bypass this error, till I figured out I should try to kill this process.

ps.: i'm on Windows 8.1
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 153
    Hello my friends, i'm glad to present you utility for installing custom recovery & root to your phone, working on stock MM .575 LB
    You don't need root on your phone to run this utility!

    How-to:
    * you need stock MM .575 or .291 firmware
    * if you have .291 firmware, you need flash stock kernel.sin (575) via FlashTool and turn on your phone. After, when script done and you reboot in custom recovery, flash SuperSU, then turn off your phone and flash back kernel.sin (291)
    * download zip and extract to your computer
    * enable USB-debugging on your phone and plug phone to computer
    * run install.bat as administrator

    When all finished your phone reboot in custom recovery.
    Then you can install any supersu.zip in custom recovery.
    Now you have last TWRP, busybox and root :good:
    Enjoy!

    FOR ALL WHO WANTS INSTALL Slimm and other custom zips with UUID METHOD READ --> THIS

    UPDATE_07.09.2016:
    * added support D5833 and D6603
    * added stock kernel for FlashTool (see attach). just change .zip to .ftf
    * TWRP with new functions like adb backup and auto-reboot (check lastest commits)
    * busybox with FULL Selinux support like setenforce, setsebool etc...
    * added clean tmp files command

    UPDATE_08.09.2016:
    * fix error with daemon (adb) - please run this .bat as administrator

    UPDATE_04.11.2016:
    * add linux installer version HERE

    UPDATE_23.01.17:
    * twrp 3.0.3 (if you are already have recovery, just copy recovery.twrp.cpio.lzma from this zip to your phone /system/etc/mm_twrp_recovery/ and replace. Don't forget chmod 644)
    * busybox 1.26.2 (to update copy busybox from this zip to your phone /system/xbin/ and replace. Don't forget chmod 755)

    UPDATE_15.03.17:
    * update TWRP to 3.1.0-0
    * added vold decryptions --> READ
    * added zip for update the current version. just flash it in recovery.
    UPDATE_13.05.2017
    * update TWRP to 3.1.1-0

    Thanks:
    @zxz0O0 for iovyroot
    @Wolfbreak for idea with recroot
    @shoey63 for show me HOW. Thanks again, bro
    @Macsek for linux installer
    19
    Good News and Bad News.
    - Bad news is the vulnerability has been patched in the new release 23.5.A.1.291.
    - Good news is new release still boots on 23.5.A.0.575 kernel.
    - Soo . . . flash new 23.5.A.1.291 firmware with flashtool, then flash only the kernel from 23.5.A.0.575 firmware, reboot and run the tool to get root and recovery, then flash only the kernel from 23.5.A.1.291 firmware
    - ????
    - Profit!
    - You will be rooted on latest firmware, even with locked bootloader, lmao.

    Edit:
    Here is a new iovyroot binary I have compiled. It needs to go in - Recovery_for_MM575 \files
    I have added support for the following 23.5.A.0.575 firmwares

    • - D5833 (Tested and working)
      - D6633 (Tested and working)
      - D6653 (Tested and working)
      - D6603 (Tested and working)
    @russel5, is it Ok if I make a thread about this in Z3 forums?
    10
    installing from linux

    Hi folks,

    I modified the windows-only method to run under linux, created install.sh (had to compress it to upload in xda, run gunzip install.sh.gz to extract).
    @russel5, can you please insert a link to this post in the 1st post, others can find it useful too.

    "Thanks! :good:" button is for free ;)
    9
    This is basically the "MM TWRP Recovery for Locked BL" I've created months ago for Z3C, Z3 and Z2, slightly modified with root solution already in the pack. Great edit!
    6
    Thread updated, enjoy.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone