Possible marshmallow root with locked boot-loader? - Sony Xperia M5

(not sure what thread to put it in)
I doubt this will work but i was using sony mobile flasher by androxyde and so my phone came up with root denied so I clicked on the root section and tried them all didn't work until i clicked on service menu and I got this
03/047/2016 19:47:53 - INFO - Pushing C:\Users\Myname\.flashTool\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\Superuser.apk to /data/local/tmp/Superuser.apk
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\install-recovery.sh to /data/local/tmp/install-recovery.sh
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\99SuperSUDaemon to /data/local/tmp/99SuperSUDaemon
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\onload.sh to /data/local/tmp/
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\getroot.sh to /data/local/tmp/
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\install-recovery.sh to /data/local/tmp/
03/048/2016 19:48:13 - INFO - Look at your phone. Choose Service Test, then Display.
03/048/2016 19:48:13 - INFO - Waiting for uevent_helper rw
03/048/2016 19:48:15 - INFO - Device connected with USB debugging on
03/048/2016 19:48:16 - INFO - Connected device : Sony Xperia M5
03/048/2016 19:48:16 - INFO - Installed version of busybox : N/A
03/048/2016 19:48:16 - INFO - Android version : 6.0 / kernel version : 3.10.72+ / Build number : 30.2.A.1.21
03/048/2016 19:48:16 - INFO - Root access denied
03/048/2016 19:48:19 - INFO - Waiting for rooted shell
03/048/2016 19:48:20 - INFO - Root achieved. Installing root files. Device will reboot. Please wait.
03/048/2016 19:48:20 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\installsu.sh to /data/local/tmp/
but I just hard bricked my phone and just got it back so I don't want to try it but if anyone is willing to try that would be great

It's simple: starting with Marshmallow update, Xperia M5 now have verified boot (dm-verity) enabled, just like all other Xperia devices from 2015 and onwards (some older Xperia devices also got dm-verity through a firmware update). That means it doesn't matter if you find a working exploit or not, modifying a single byte of the system partition will simply fail dm-verity checks and as result your phone won't boot (that's apparently what happened to your phone, you managed to modify the system partition and as result it refused to boot). No write access to system partition means no way to install su binary and other required files.
In other words, the ages of root with a locked bootloader are gone, unlocking the bootloader (so you can flash a modified kernel with dm-verity disabled or a systemless root solution) is the only way to get root now.

mbc07 said:
It's simple: starting with Marshmallow update, Xperia M5 now have verified boot (dm-verity) enabled, just like all other Xperia devices from 2015 and onwards (some older Xperia devices also got dm-verity through a firmware update). That means it doesn't matter if you find a working exploit or not, modifying a single byte of the system partition will simply fail dm-verity checks and as result your phone won't boot (that's apparently what happened to your phone, you managed to modify the system partition and as result it refused to boot). No write access to system partition means no way to install su binary and other required files.
In other words, the ages of root with a locked bootloader are gone, unlocking the bootloader (so you can flash a modified kernel with dm-verity disabled or a systemless root solution) is the only way to get root now.
Click to expand...
Click to collapse
I bricked my phone because I'm an idiot not because of that and I was on lollipop when I did it

"Hard bricked and got it back" - HOW?????
ih8redsn0w said:
(not sure what thread to put it in)
... but I just hard bricked my phone and just got it back ...
Click to expand...
Click to collapse
Hi there, this quote is extremely interesting!
What do you mean with "just got it back"? Got it back to booting...? Or got it back from a warranty repair?
Please let us know what we have to do to get our's back too... I hard bricked mine and don't seem to find a way to unbrick it. And more of us with the same problem are out there... THANKS indeed!

Related

Error when rooting phone FTError

I just flashed to LT15i_4.0.2.A.0.62_Generic Global World and when I use flashtools to uroot I get
05/007/2012 02:07:52 - INFO - <- This level is successfully initialized
05/007/2012 02:07:52 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
05/007/2012 02:07:52 - INFO - You can drag and drop ftf files here to start flashing them
05/007/2012 02:07:57 - INFO - Device connected with USB debugging on
05/008/2012 02:08:00 - INFO - Connected device : LT15
05/008/2012 02:08:00 - INFO - Installed version of busybox : N/A
05/008/2012 02:08:00 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
05/008/2012 02:08:01 - INFO - Pushing C:\Flashtool\.\devices\LT15\busybox\1.19.0\busybox to /data/local/tmp/busybox
05/008/2012 02:08:03 - INFO - Pushing C:\Flashtool\.\custom\root\zergrush.tar.uue to /data/local/tmp
05/008/2012 02:08:04 - INFO - Running part1 of Root Exploit, please wait
05/008/2012 02:08:26 - INFO - Waiting for device
05/009/2012 02:09:26 - INFO - Forced stop waiting.
05/009/2012 02:09:26 - INFO - Running part2 of Root Exploit
05/009/2012 02:09:26 - INFO - Running rootit2
05/009/2012 02:09:27 - ERROR - Cleaning rootit files
Mounting /system R/W
FTError
.62 can't be rooted by any method yet. Either flash a pre-rooted kernel if you have an unlocked bootloader, if not flash.42, root then ota update.
sinkster said:
.62 can't be rooted by any method yet. Either flash a pre-rooted kernel if you have an unlocked bootloader, if not flash.42, root then ota update.
Click to expand...
Click to collapse
I have a locked bootloader. I flashed .42, rooted it, but OTA still failed.
If you keep attempting the ota then it will eventually complete, apparently.
See my post here:
http://forum.xda-developers.com/showpost.php?p=23285407&postcount=15
sinkster said:
If you keep attempting the ota then it will eventually complete, apparently.
Click to expand...
Click to collapse
Yes it did.
hi mate, if you are on 0.62, then just flash an old kernel using flashtool and then you would be able to root 0.62 as well
or have a look at this
http://talk.sonymobile.com/message/142493#142493

Unable to root Xperia Play

I just lost one entire afternoon trying to gain root access to my Xperia Play!
Basically I need to get rid of all the weird apps that came with it, like the chinesse keyboard
I also want to choose a different location to use the sony store for psone games
I tried everything I could find:
gingerbread did nothing for over 30 minutes
superoneclick, using zergrush exploid gets stuck at step 7: waiting for device
with psneuter it freezes at step 5: waiting for device
RootXperiaPlay apparently worked, but when it try to install the superuser app the cmd window say that its a read only file and it does do nothing at all
fastboot didnt work either, I got the unlock key from sony and everything. actually this one flashed my cellphone and now its back to factory conditions, thank god for the gmail contacts. Sadly, this means that I also lost progress in all of my games and, what is worse, the zelda ocarina of time save file, roms and apk for muppen64 xp (the emulator) which is no longer in the play store.
Flashtool didnt work, there is its log
22/044/2012 23:44:35 - INFO - Device connected with USB debugging on
22/044/2012 23:44:36 - INFO - Connected device : R800
22/044/2012 23:44:36 - INFO - Installed version of busybox : N/A
22/044/2012 23:44:36 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
22/044/2012 23:44:42 - INFO - Pushing C:\Flashtool\.\devices\R800\busybox\1.19.0\busybox to /data/local/tmp/busybox
22/044/2012 23:44:43 - INFO - Pushing C:\Flashtool\.\custom\root\zergrush.tar.uue to /data/local/tmp
22/044/2012 23:44:44 - INFO - Running part1 of Root Exploit, please wait
22/045/2012 23:45:04 - INFO - Waiting for device
22/046/2012 23:46:04 - INFO - Forced stop waiting.
22/046/2012 23:46:04 - INFO - Running part2 of Root Exploit
22/046/2012 23:46:04 - INFO - Running rootit2
22/046/2012 23:46:04 - ERROR - Cleaning rootit files
Mounting /system R/W
FTError
Xperia play, R800i, 2.3.4 build 4.0.2.A.0.69
Any tip will be appreciated.
Thanks!
Ugh, not this again. You have firmware 4.0.2.A.0.69, which is UNROOTABLE. Downgrade to 4.0.2.A.0.58 or lower, then you can root it. Please search first
oops
sorry for that, yesterday I searched everywhere, all other examples had other builds version but didn't say anything about this one

[Q] Root help needed!

hi,
i need help rooting my xperia plat at&t.
the main issue im having is:
- do i need to unlock the bootloader?
when i type the code: *#*#7378423#*#* to see if my bootloader is unlockable, i dont see anytrhing under: Service info > Configuration > Rooting Status. If Bootloader unlock allowed
as a matter of fact, there is no rooting status folder at all. hmmmm
then when i put my play into fastboot mode, the light is green, not blue. im holding down the back button. thats the correct one right?
i just want to flash a rom, thats all.
also, flash tool for my mac is not working correctly, it says:
26/005/2013 16:05:36 - INFO - <- This level is successfully initialized
26/005/2013 16:05:36 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 22:58:57
26/005/2013 16:05:36 - INFO - You can drag and drop ftf files here to start flashing them
26/005/2013 16:05:43 - INFO - Device connected with USB debugging on
26/005/2013 16:05:45 - INFO - Connected device : R800
26/005/2013 16:05:45 - INFO - Installed version of busybox : N/A
26/005/2013 16:05:45 - INFO - Android version : 2.3.3 / kernel version : 2.6.32.9-perf / Build number : 3.0.1.B.0.285
26/005/2013 16:05:49 - INFO - Device connected with USB debugging on
26/005/2013 16:05:50 - INFO - Decrypting /Applications/FlashTool.app/Contents/MacOS/custom/root/ZergRush/zergrush.tar.uue.enc to /Applications/FlashTool.app/Contents/MacOS/custom/root/ZergRush/zergrush.tar.uue
26/005/2013 16:05:51 - INFO - Connected device : R800
26/005/2013 16:05:51 - INFO - Installed version of busybox : N/A
26/005/2013 16:05:51 - INFO - Android version : 2.3.3 / kernel version : 2.6.32.9-perf / Build number : 3.0.1.B.0.285
26/005/2013 16:05:54 - INFO - Pushing /Applications/FlashTool.app/Contents/MacOS/custom/root/ZergRush/zergrush.tar.uue to /data/local/tmp
26/005/2013 16:05:54 - INFO - Pushing /Applications/FlashTool.app/Contents/MacOS/./devices/R800/busybox/1.20.2/busybox to /data/local/tmp/busybox
26/005/2013 16:05:55 - INFO - Pushing /Applications/FlashTool.app/Contents/MacOS/custom/root/subin/Superuser/su to /data/local/tmp/su
26/005/2013 16:05:55 - INFO - Pushing /Applications/FlashTool.app/Contents/MacOS/custom/root/subin/Superuser/Superuser.apk to /data/local/tmp/Superuser.apk
26/005/2013 16:05:57 - INFO - Running part1 of Root Exploit, please wait
26/006/2013 16:06:16 - INFO - Waiting for device. After 60secs, stop waiting will be forced
26/008/2013 16:08:10 - INFO - Device connected with USB debugging on
26/008/2013 16:08:15 - ERROR - The part1 exploit did not work
26/008/2013 16:08:15 - INFO - Cleaning files
any thoughts/comments/help would be very nice.
thanks,
Alex
First of all the entry in the Service menu is for the bootloader and has nothing to do with rooting your Phone. The bootloader is comparable to the bios in a pc. What you want, is to gain access to the root fodler of your device which is read-only by default.
Holding back puts the device in flashmode not fastboot-mode (which you dont want). Green=flash Blue=fastboot
Easiest way to root is to use flashtool: http://forum.xda-developers.com/showthread.php?t=1351299
Luxxuor said:
First of all the entry in the Service menu is for the bootloader and has nothing to do with rooting your Phone. The bootloader is comparable to the bios in a pc. What you want, is to gain access to the root fodler of your device which is read-only by default.
Holding back puts the device in flashmode not fastboot-mode (which you dont want). Green=flash Blue=fastboot
Easiest way to root is to use flashtool: http://forum.xda-developers.com/showthread.php?t=1351299
Click to expand...
Click to collapse
like i said, it wont work.
did you see the list of info i get???

OFFICIAL UPDATED Flashtool 0.9.13.0 for ALL XPERIA (Windows)

Latest Flashtool 0.9.13.0 for ALL XPERIA (Windows)
Windows Edition - v0.9.11.0 - MD5 : A0F880F3CF420A31D86026F49A2013D7
Updated on 12/06/2013 ©2011 by Androxyde
More information at http://androxyde.github.com/
Flashtool Release Notes:
* 0.9.13
This version is a big split with every previous ones.
And not fully featured as previous can be.
I changed the UI framework from Swing to SWT because of a better integration with Mac UI.
Here is what is missing from previous releases :
- No multilingual UI
- No recovery installer
- No kernel installer (for 2010 devices)
- No ROM cleaner.
- Cannot Add/Edit/Remove devices.
No TA hex editor (in pro mode)
Version fully compatible with all 2013 devices (Z1/Z Ultra/Tablet Z etc etc)
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
As for flashing, BLU is available even without any connected device, even with
unrecognized devices.
Updated SuperSU package. Added servicemnu root hack
(works with Z1/Z Ultra)
Known working for Xperia T/V too
Added TA partition backup/restore. Using this feature, you can backup TA before unlock.
Restore TA will relock the devicee and get DRM back as well as BE2
(full complete relock). You cannot count on this feature if ever your device is
already unlocked. Missuse of this feature can brick the device
Introduction to Flashtool:
Flashtool is a flashing software that can be used to :
1. Flash original Images (Android 1.6, 2.1, 2.3 Images)
2. Root your phone
3. Install Recovery, Busybox, custom kernels
4. Clean your Rom (remove /system/apps apps of your choice)
(Be careful, unless you really know what you do, do not modify the default list.
This can make your phone stuck at the SE Logo)
5. Clear dalvik cache
6. Optimize (install of JIT v2)
(Disabled in 0.4, will readd it as a plugin for 2.1 phones only)
7. Customize (installs apps found in the custom/apps folder of the flashtool)
8. Clean uninstalled (remove any references to system apps removed in the
Clean (root needed) step)
9. Edit any text file on the device
10. Rebrand your device
Download Link
https://mega.co.nz/#!d4lx1bZQ!Ltt8Bw...Rvh0Z2ZMl-kCn0
Thanks for mirror @marco.it
FAQ.
Q : Can Flashtool unlock bootloader for a first time unlock ?
A : Yes, it does it using official sony method (get key, then issue the right fastboot command)
Q : Can Flashtool relock bootloader ?
A : Yes
Q : Can Flashtool unlock bootloader after a relock ?
A : Yes.
With this release, before unlocking first time, root your device and you will be able to backup your TA partition (Raw ta backup). By doing this, you will be able to relock / restore your TA partition and have back BE2 and all DRM keys.
Happy flashing
HIT THANKS BUTTON IF IT HELPED
majeed619 said:
Latest Flashtool 0.9.11.0 for ALL XPERIA (Windows)
Windows Edition - v0.9.11.0 - MD5 : A0F880F3CF420A31D86026F49A2013D7
Updated on 12/06/2013 ©2011 by Androxyde
More information at http://androxyde.github.com/
Flashtool Release Notes:
* 0.9.11
This version is a big split with every previous ones.
And not fully featured as previous can be.
I changed the UI framework from Swing to SWT because of a better integration with Mac UI.
Here is what is missing from previous releases :
- No multilingual UI
- No recovery installer
- No kernel installer (for 2010 devices)
- No ROM cleaner.
- Cannot Add/Edit/Remove devices.
No TA hex editor (in pro mode)
Version fully compatible with all 2013 devices (Z/ZL/Tablet Z etc etc)
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
As for flashing, BLU is available even without any connected device, even with
unrecognized devices.
Updated SuperSU package. Added servicemnu root hack
(works with Z/ZL for all FW up to .434)
Known working for Xperia T/V too
Added TA partition backup/restore. Using this feature, you can backup TA before unlock.
Restore TA will relock the devicee and get DRM back as well as BE2
(full complete relock). You cannot count on this feature if ever your device is
already unlocked. Missuse of this feature can brick the device
Introduction to Flashtool:
Flashtool is a flashing software that can be used to :
1. Flash original Images (Android 1.6, 2.1, 2.3 Images)
2. Root your phone
3. Install Recovery, Busybox, custom kernels
4. Clean your Rom (remove /system/apps apps of your choice)
(Be careful, unless you really know what you do, do not modify the default list.
This can make your phone stuck at the SE Logo)
5. Clear dalvik cache
6. Optimize (install of JIT v2)
(Disabled in 0.4, will readd it as a plugin for 2.1 phones only)
7. Customize (installs apps found in the custom/apps folder of the flashtool)
8. Clean uninstalled (remove any references to system apps removed in the
Clean (root needed) step)
9. Edit any text file on the device
10. Rebrand your device
Download Link
http://sdrv.ms/ZJN81O
HIT THANKS BUTTON IF IT HELPED
Click to expand...
Click to collapse
THANK YOU! Every link I was finding was around a 45 min download!
thanks for the link.. i hope that i finally can unbrick my ZQ -.- he's stucked in Sony logo
http://postimg.org/image/jnx079uwd/
I have problem downloading flashtool driver of xperia arc s
As you can see I attached picture.
Bassheadzero said:
thanks for the link.. i hope that i finally can unbrick my ZQ -.- he's stucked in Sony logo
Click to expand...
Click to collapse
Just simply flash the compatible ftf file for your device using flashtool
Your phone will be fine I faced the same issue few weeks back
sanjulgupta said:
Just simply flash the compatible ftf file for your device using flashtool
Your phone will be fine I faced the same issue few weeks back
Click to expand...
Click to collapse
Oh many thanks mate, I already get solved this problem flashing a ftf fw!
Cherrs!
This may be a dumb question, but I'll ask it anyways.
I have an Xperia ZL that was purchased from bell. I know it has a locked bootloader that cannot be unlocked through the official Sony tool, so i'm wondering if it can be unlocked with this flashtool?
If so that would be awesome.
If not, I'll be supremely unimpressed with Sony.
Sent from my C6506 using xda premium
Folder is empty! Kindly re-upload.
I agree
Folder is empty
Hey guys, after some serious digging, I found it here. http://www.flashtool.net/download.html
-NM
stevessvt said:
Hey guys, after some serious digging, I found it here. http://www.flashtool.net/download.html
Click to expand...
Click to collapse
not a valid windows 32 application.
alex4659 said:
not a valid windows 32 application.
Click to expand...
Click to collapse
Really? Did you try this version of it?
Windows Edition : v0.9.11.0 – MD5 : A0F880F3CF420A31D86026F49A2013D7
It worked just fine for me and several others.
Folder is empty , Kindly reupload and update the links
stevessvt said:
Really? Did you try this version of it?
Windows Edition : v0.9.11.0 – MD5 : A0F880F3CF420A31D86026F49A2013D7
It worked just fine for me and several others.
Click to expand...
Click to collapse
yes i did.
im using parallels desk top for mac so im downloading it for my macbook pro as well.
you dont by chance have a direct link to a ftf to a pre rooted firmware (i think gingerbread) for the xperia x10s do you?
thanks again,
Alex
---------- Post added at 08:47 PM ---------- Previous post was at 08:39 PM ----------
this is what i get when i try to flash the kernel-4.3-v21.ftf:
Note, my phone is stuck at the sony ericsson screen
27/044/2013 20:44:23 - INFO - <- This level is successfully initialized
27/044/2013 20:44:23 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
27/044/2013 20:44:23 - INFO - libusb version 1.0.15
27/044/2013 20:44:27 - INFO - Device disconnected
27/044/2013 20:44:39 - INFO - Selected es209ra / 21 / 4.3.X
27/044/2013 20:44:39 - INFO - Preparing files for flashing
27/044/2013 20:44:39 - INFO - Please connect your device into flashmode.
27/044/2013 20:44:49 - INFO - Device connected in flash mode
27/044/2013 20:44:50 - INFO - Opening device for R/W
27/044/2013 20:44:50 - INFO - Device connected in flash mode
27/044/2013 20:44:50 - INFO - Device ready for R/W.
27/044/2013 20:44:50 - INFO - Reading device information
27/044/2013 20:44:50 - INFO - Phone ready for flashmode operations.
27/044/2013 20:44:51 - INFO - Current device : X10i - CB511PDEG8 - 1241-1846_R1C - 1227-4612_3.0.1.G.0.75 - WORLD-1-4-8_3.0.1.G.0.75
27/044/2013 20:44:51 - INFO - Start Flashing
27/044/2013 20:44:51 - INFO - Processing loader
27/044/2013 20:44:51 - INFO - Checking header
27/044/2013 20:44:51 - INFO - Ending flash session
27/044/2013 20:44:51 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
27/044/2013 20:44:51 - ERROR - Error flashing. Aborted
27/044/2013 20:44:51 - INFO - Device connected in flash mode
27/044/2013 20:44:53 - INFO - Device disconnected
27/044/2013 20:44:55 - INFO - Device connected in flash mode
27/044/2013 20:44:59 - INFO - Device disconnected
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
SnakeEyesNinja said:
Folder is empty , Kindly reupload and update the links
Click to expand...
Click to collapse
dito
Mega.co.nz mirror:
https://mega.co.nz/#!d4lx1bZQ!Ltt8BwMnkRTWPUNzZDwZ7AzIDaEGLRvh0Z2ZMl-kCn0
with this version of Flash tool i'm not seeing a xperia ion option. Is there another phone that is identical to mine within those options?
montrese04 said:
with this version of Flash tool i'm not seeing a xperia ion option. Is there another phone that is identical to mine within those options?
Click to expand...
Click to collapse
HOPE IT WORKS :good:
http://forum.xda-developers.com/showthread.php?t=1812168
ERROR SIN verification failed
I have a question about flashtool 0.9.13.0:
What does mean 'SIN verification failed'? Is there a problem in the ftf file itself, in the configuration of flashtool or between ftf file and phone (baseband, bootloader, etc)?
Thanks for any hints,
Alexej

[Tool] iovySU - Root your device without unlocking its bootloader

Reminder: iovySU works only on select Lollipop-based firmwares from Xperia M5, if you updated your phone to Android 6.0, the only way to get root is by unlocking its bootloader and flashing a custom kernel, like this one. If your phone has a permanently locked bootloader, there's NO WAY to root while running Marshmallow, but you can still downgrade to Lollipop and use iovySU if you desperately need root access on your bootloader locked M5.
Today I present you iovySU, a tool based on iovyroot binary which can sucessfully root Xperia M5 family! No need to unlock your bootloader or lose your unique DRM keys!
Requirements
• You must be using one of the supported firmwares (they're listed on "Supported Firmwares" down below and are also available as FTF, so you can downgrade with Androxyde's FlashTool if needed).
• USB Debugging must be enabled on the phone (available in Settings => Developer Settings -- if you can't see it, go to Settings => About Phone and tap 7 times on Android Build).
• ADB drivers should be installed on the computer, otherwise this tool won't see it (you can install Xperia Companion to get the drivers or use the stand-alone ADB driver).
• Your computer should be running Windows or Linux (you can probably use the Linux script on Mac, but that's completely untested and not guaranteed to work at all).
Instructions
• Download the attached ZIP and unzip its contents somewhere;
• Connect your phone, open iovysu.bat and wait (if you're on Linux, launch iovysu.sh from Terminal instead);
• After the process finished, the tool will notify you, press any key to reboot your phone;
• If iovySU worked, on your phone you should see a SuperSU notification, tap on it and let it update the binary (if you don't see the SuperSU notification, open SuperSU from app drawer instead);
• After updating the binary, reboot your phone once more and enjoy your fully rooted phone!
Supported Firmwares
For single SIM variants (E5603, E5606 and E5653):
• 30.0.A.1.23
• 30.1.A.1.33
For dual SIM variants (E5633, E5643 and E5663):
• 30.0.B.1.23
• 30.1.B.1.33
Frequently Asked Questions
Q: Help! I've enabled USB Debugging on my phone but iovySU keeps stuck at "Waiting for device" message!
A: This means ADB isn't "seeing" your phone, either because you didn't install ADB drivers (you can use this stand-alone driver) or because you didn't authorize the connection on your phone. If iovySU still can't see your phone, make sure you don't have another Android device with USB Debugging enabled plugged on your computer at the same time or emulators like BlueStacks or Genymotion running.
Q: Help! I'm using one of the supported firmwares, I ran iovySU, it rebooted my phone but I still don't have root access/SuperSU didn't show up in the app drawer!
A: Run iovySU again. Sometimes the exploit may freeze and your phone may reboot before SuperSU gets installed. In case you tried a few times and still can't get root, post the output of the tool here so I can help you.
Q: Help! I'm using a newer firmware but I couldn't find an FTF of a supported firmware version which matches my variant! What can I do?
A: I've uploaded the FTFs of the supported firmwares (check the forum), you can crossflash them safely to your phone (just don't do single SIM => dual SIM or vice versa -- the phone will bootloop). After rooting with iovySU, get an FTF which matches your variant/region with XperiFirm/FlashTool and use dd Flasher Minimal to flash it while maintaining root access.
Q: Why should I use this instead of KingRoot?
A: Mainly because it's open source, so you can see what's actually being modified on your phone. Currently, KingRoot has the convenience of rooting Xperia M5 with one click but on the other hand you get a dubious root managing app that have issues with some root-enabled apps and also includes other bloat stuff built-in. Although with some effort it can be replaced with SuperSU, the process is not that simple and can still leave junk on your system. That's also the main reason I talked with @zxz0O0 as soon as I noticed iovyroot could work on Xperia M5.
Q: I used iovySU and I'm rooted now, but I'm stuck on an older firmware version/another variant and OTAs fail to install. How can I update without losing root access?
A: By using my other tool, dd Flasher Minimal. If you crossflashed your phone in order to use iovySU, just get an FTF that matches your variant/region with FlashTool/XperiFirm and use it with dd Flasher Minimal.
Q: Is there any difference between iovySU and iovyroot?
A: Yes and no. Basically, the only difference between iovySU and iovyroot is that iovyroot gains temporary root to make a TA backup of the supported devices, while iovySU benefits from the same temporary root but to actually install SuperSU permanently on the system. The reason iovyroot script only backups TA partition is that many of the supported devices have additional security measures enabled, like dm-verity, so, these devices would refuse to boot if a single byte was modified on the system partition (and well, you actually need to write into system partition to get permanent root). For our luck, none of the Xperia M5 firmwares available at the moment have dm-verity, so we can get full root access without any issues!
Q: Can I use iovySU to root <insert device here>?
A: Well, if it's a device supported by iovyroot, without dm-verity (or similiar) on its kernel and running an ARM64 version of Android Lollipop or newer, then yes, it should work. It theoretically can work also with 32-bit devices, but then you'll need to modify the SuperSU package used by iovySU with the appropriate binaries (that's because unlikely the official SuperSU package, iovySU uses a stripped down version including only the bare minimum needed to get SuperSU installed on an ARM64 ROM).
Credits
I'm the author of the script but it also includes pieces of code made by @Chainfire (SuperSU) and heavily relies on iovyroot binary. I would also like to thank the people who helped testing the exploit earlier and @zxz0O0 for developing the iovyroot binary and his promptly help in adding Xperia M5 support to it.
worked for me on 30.1.A.1.33 PERFECTLY!
Please note: I was using nova launcher, I had to Change back to Default xperia launcher for iovySU to work
Thank you!
Ok I managed to get root with this, but something odd happened. So I tried to Root with KingRoot beforehand, but it didn't work and I couldn't uninstall the app. So when I tried to use ivorySU today, after reboot the screen froze on startup forcing me to do a hard reset. After doing that and rebooting I had gained access to Root with KingRoot, but I didn't have SuperSU. What proceeds now? I really want SuperSU instead of KingRoot. I'm kinda new at this, sorry if this is a noobish question.
I'm on a E5606 model, Firmware: 30.1.A.1.33.
@Neofranky, I strongly suggest flashing a FTF suitable to your device to restore your system partition to clean state then try iovySU directly. If you try using iovySU after trying KingRoot, it may leave you with their su version and then, by running iovySU, it would detect that as an already rooted device, thus doing nothing.
Or, now that you have root (even through it's from KingRoot and not SuperSU) you could use dd Flasher Minimal with a FTF of a newer firmware (or from the same firmware if 30.1.A.1.55 wasn't released on your region yet), that would also restore your system partition to a clean state + SuperSU, wiping KingRoot completely...
will this work for c5 E5553 5.1?
@gsser, currently, no. Before trying anything, your phone must be supported by iovyroot (in other words, it should have a Lollipop kernel with build date of Deceber 2015 or earlier). Then, after having iovyroot support it must not have dm-verity enabled on its kernel, otherwise iovySU won't work (however you would still be able to backup your TA Partition with the main iovyroot in that case). If your phone meets those requirements, you can talk with @zxz0O0 to see if support for your phone can be added in iovyroot...
Problem to root with iovyhu
Hi everybody, i'm stuck when i run the .bat on win 10 64, i have an NTFS partition, put the folder on my D: drive, changed permisions to run as a administrator ans nothing, i just got a windows that say path not found:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i've tried tu run it from a fat32 usb, and got the same result.
i am using the 30.1.A.1.33 for 5603 xperia M5, even reflashed twice the cellphone.
can you tell me what I am doing wrong. thanks ins advance.
hectorgironc said:
can you tell me what I am doing wrong. thanks ins advance.
Click to expand...
Click to collapse
You're running the .bat as Administrator, that's what you're doing wrong. When you call a .bat file as admin (not just iovySU, this applies to any .bat), Windows will set the working path as something like C:\Windows\System32 and that's why it fails, iovySU files aren't on the system folder. So, either run the .bat directly or manually navigate to the folder where iovySU is located with an elevated Command Prompt before running it if you really need or want to run with elevated privileges...
I all, how can I unroot my device? Thank you
I believe that the best way to unroot is to use flashtool to install a stock ROM.
In the method above you used flashtool to install everything but the system file. This even install that file.
mbc07
Thanks for the fast answer, I did it as you told me, opened a CMD window with Adminstrator Rights, entered to the iovusy follder, but the Iovysu.bat keeps in waiting mode:
My settings on my phone are Developer mode activated, USB debugging activated, in security page Unkown sources are allowed.
I dunno but, here at work i Have Win 7 64 bits, At home is Win 10 64 bits and Linux Mint, Haven´t tried on lunix due it does not recognize my phone ( I am a little bit lamer with LINUX yet =P), Can anybody tell me a OS Setting that worked?
This is the first time a phone gives me a lot of trouble, is my fourth android phone. =\
Regards.
@hectorgironc you either didn't install ADB drivers correctly or didn't authorize the computer on the phone...
@vatastala there's various methods for unrooting, you can choose full unroot option inside SuperSU settings, flash a FTF with Androxyde's Flashtool or perform a repair through Xperia Companion, for example...
OK, finally after several tests installing android SDK's, google drivers, java sre as some forums commented... even I offered a chicken sacrifice to the gods, the only thing worked to me was to install the adb drivers for the m5 from developers xperia page:
http://developer.sonymobile.com/downloads/drivers/
just scroll until you find xperia m5 drivers, is about 8.5 MB, or download it from here.
after that everything was a charm. thanks for your help mbc07 :good:
mbc07 said:
Today I present you iovySU, a tool based on iovyroot binary which can sucessfully root Xperia M5 family! No need to unlock your bootloader or lose your unique DRM keys!
Requirements
• You must be using one of the supported firmwares (they're listed on "Supported Firmwares" down below and are also available as FTF, so you can downgrade with Androxyde's FlashTool if needed).
• USB Debugging must be enabled on the phone (available in Settings => Developer Settings -- if you can't see it, go to Settings => About Phone and tap 7 times on Android Build).
• ADB drivers should be installed on the computer, otherwise this tool won't see it (you can install Xperia Companion to get the drivers or use the stand-alone ADB driver).
• Your computer should be running Windows or Linux (you can probably use the Linux script on Mac, but that's completely untested and not guaranteed to work at all).
Instructions
• Download the attached ZIP and unzip its contents somewhere;
• Connect your phone, open iovysu.bat and wait (if you're on Linux, launch iovysu.sh from Terminal instead);
• After the process finished, the tool will notify you, press any key to reboot your phone;
• If iovySU worked, on your phone you should see a SuperSU notification, tap on it and let it update the binary (if you don't see the SuperSU notification, open SuperSU from app drawer instead);
• After updating the binary, reboot your phone once more and enjoy your fully rooted phone!
Supported Firmwares
For single SIM variants (E5603, E5606 and E5653):
• 30.0.A.1.23
• 30.1.A.1.33
For dual SIM variants (E5633, E5643 and E5663):
• 30.0.B.1.23
• 30.1.B.1.33
Frequently Asked Questions
Q: Help! I've enabled USB Debugging on my phone but iovySU keeps stuck at "Waiting for device" message!
A: This means ADB isn't "seeing" your phone, either because you didn't install ADB drivers (you can use this stand-alone driver) or because you didn't authorize the connection on your phone. If iovySU still can't see your phone, make sure you don't have another Android device with USB Debugging enabled plugged on your computer at the same time or emulators like BlueStacks or Genymotion running.
Q: Help! I'm using one of the supported firmwares, I ran iovySU, it rebooted my phone but I still don't have root access/SuperSU didn't show up in the app drawer!
A: Run iovySU again. Sometimes the exploit may freeze and your phone may reboot before SuperSU gets installed. In case you tried a few times and still can't get root, post the output of the tool here so I can help you.
Q: Help! I'm using a newer firmware but I couldn't find an FTF of a supported firmware version which matches my variant! What can I do?
A: I've uploaded the FTFs of the supported firmwares (check the forum), you can crossflash them safely to your phone (just don't do single SIM => dual SIM or vice versa -- the phone will bootloop). After rooting with iovySU, get an FTF which matches your variant/region with XperiFirm/FlashTool and use dd Flasher Minimal to flash it while maintaining root access.
Q: Why should I use this instead of KingRoot?
A: Mainly because it's open source, so you can see what's actually being modified on your phone. Currently, KingRoot has the convenience of rooting Xperia M5 with one click but on the other hand you get a dubious root managing app that have issues with some root-enabled apps and also includes other bloat stuff built-in. Although with some effort it can be replaced with SuperSU, the process is not that simple and can still leave junk on your system. That's also the main reason I talked with @zxz0O0 as soon as I noticed iovyroot could work on Xperia M5.
Q: I used iovySU and I'm rooted now, but I'm stuck on an older firmware version/another variant and OTAs fail to install. How can I update without losing root access?
A: By using my other tool, dd Flasher Minimal. If you crossflashed your phone in order to use iovySU, just get an FTF that matches your variant/region with FlashTool/XperiFirm and use it with dd Flasher Minimal.
Q: Is there any difference between iovySU and iovyroot?
A: Yes and no. Basically, the only difference between iovySU and iovyroot is that iovyroot gains temporary root to make a TA backup of the supported devices, while iovySU benefits from the same temporary root but to actually install SuperSU permanently on the system. The reason iovyroot script only backups TA partition is that many of the supported devices have additional security measures enabled, like dm-verity, so, these devices would refuse to boot if a single byte was modified on the system partition (and well, you actually need to write into system partition to get permanent root). For our luck, none of the Xperia M5 firmwares available at the moment have dm-verity, so we can get full root access without any issues!
Q: Can I use iovySU to root <insert device here>?
A: Well, if it's a device supported by iovyroot, without dm-verity (or similiar) on its kernel and running an ARM64 version of Android Lollipop or newer, then yes, it should work. It theoretically can work also with 32-bit devices, but then you'll need to modify the SuperSU package used by iovySU with the appropriate binaries (that's because unlikely the official SuperSU package, iovySU uses a stripped down version including only the bare minimum needed to get SuperSU installed on an ARM64 ROM).
Credits
I'm the author of the script but it also includes pieces of code made by @Chainfire (SuperSU) and heavily relies on iovyroot binary. I would also like to thank the people who helped testing the exploit earlier and @zxz0O0 for developing the iovyroot binary and his promptly help in adding Xperia M5 support to it.
Click to expand...
Click to collapse
Hi for my ask,
Your firmware is support with flashtool 0.9.21.0 or no, beause i flash with flashtool and brick my device 4 times, and sent to Sony Center 4 times, now I am very afraid to use flashtool with M5
If use flashtool 0.9.21.0 it have use .fsc script or not with your firmware
Thanks
The fsc file is now built into the package that flash tool gets from xperifirm. So unlike 20 you no longer get a prompt
icstm said:
The fsc file is now built into the package that flash tool gets from xperifirm. So unlike 20 you no longer get a prompt
Click to expand...
Click to collapse
Thanks so much, i just up flashtool 0.9.22.1, it's ok now flashtool have changelog:
C4 and C5 users please do not flash using Flashtool. It will brick the device. M5 users please do use FSC when flashing or it will brick your device
i hope flash it ok
Hi thanks for the hard work.
I just upgraded to marshmallow firmware through Sony companion. Means no root.
1) Any chance for me to revert back to 5.1 using customised FTF you supplied with flashtool?
2) If above yes, then root will be applied as per your instructions. Is root maintained if I flash the marshmallows using dd tool?
Waiting your response.
Downgrading with Androxyde's Flashtool to one of the old exploitable firmwares then using dd Flasher Minimal to go to the latest Lollipop firmware still works fine. Just don't use dd Flasher Minimal with the Marshmallow firmware, it'll bootloop because of dm-verity...
mbc07 said:
Downgrading with Androxyde's Flashtool to one of the old exploitable firmwares then using dd Flasher Minimal to go to the latest Lollipop firmware still works fine. Just don't use dd Flasher Minimal with the Marshmallow firmware, it'll bootloop because of dm-verity...
Click to expand...
Click to collapse
Can i downgrade without wiping userdata? Any possible side effects of doing it?
Bennybtc said:
Can i downgrade without wiping userdata? Any possible side effects of doing it?
Click to expand...
Click to collapse
From my past experience with other devices, downgrading without wiping user data will result in a bootloop, or, in the rare occasion it actually complete the boot, all apps will keep FCing and the phone will be unusable. The only cases where keeping user data don't yield issues is when you upgrade to a newer or to the same Android version...

Categories

Resources