yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] marvinalnashi:
When I use the recovery.img on the build site, I get an error.

We probably need more files including the fstab.

I extracted the stock Dutch firmware, but I'll have to pull the required files of it.
[General Questions and Answers] GameboyZA:
recovery.fstab from flastools f3311 https://www.sendspace.com/file/4uhc46
[General Questions and Answers] gautamrajput185:
Dont unlock your bootloader if you want bravia-engine 2 on your phone really working on videos

Works on mx player too

Go here

https://xdaforums.com/crossdevice-dev/sony/bravia-engine-2-gautam-rajput-t3533202
[General Questions and Answers] garikay:
I read all the posts.All You have written here is wrong. You can not install recovery in the stock kernel. You Get bootloop. I know jemmini, he does only work recovery. To install recovery must have a modified kernel. Then you will not get bootloop. And you can do on your device root. As far as I know there is no stock kernel on your device , not something that is modified. I try to make a stock kernel for your device from the source code. I compiled zimage and rawdisk.img. But I can not pack them in boot.img using mkbootim in console. Packaging in the Android kitchen it turns bootloop. It seems that I do not right and I need help.But I know that if you want to succeed you need to:

1. Get a stock kernel

2. Modify it to install recovery, root, etc.

3. Install recovery, root, etc

No other way.
[General Questions and Answers] marvinalnashi:
I'm having a look in the stock ftf, I think the kernel is hidden somewhere in there in the form of .sin .

But I don't have a good experience with kernels, so how do you modify it? I don't have Linux or anything.
[General Questions and Answers] ch3mn3y:
I don't think You can mod .sin file. But there should be sources on GitHub for kernel compiling.

And Linux is easy to install. Download VirtualBox and You don't need additional partition(s).
[General Questions and Answers] toinedu27:
You can also look at the uncompiled sources on the Sony dev website. I try to use this but i can't find that (i dont know how..)
[General Questions and Answers] garikay:
I have now zImage and rawdisk to build the kernel. But I do not have header of kernel and I do not have this device to work with him. I can put it here, maybe anyone make header and pack kernel in a Carliv Android kitchen ?
[General Questions and Answers] marvinalnashi:
There's an option in flashtool to extract the header, it should be next to raw dump.
[General Questions and Answers] marvinalnashi:
I realised that the developer of the twrp for this device hasn't added the ability to tethered boot it, the recovery has to be rebuilt in order to make it at least boot, so we can get on to the zip flashing.

For a permanent recovery we'll need to modify the kernel to support it and disable dm-verity and sony bootloader check within it.

But as we are trying to gain root access, only booting the recovery is enough.

I have a tablet which I rooted by tethered booting up a compatible cwm recovery and flashing supersu.

In short, that recovery must be modified or a new one has to be built! And I'm not going to do that cause my pc isn't capable of doing so.

Anyone who has a compatible BOOTABLE TEMPORARY recovery can send me a private message so I'll figure out the rooting process.
[General Questions and Answers] garikay:
No need to reinvent the wheel. Just have to do - make modified kernel. In ramdisk in kernel need to modify two files - build.prop and fstab.mt6735 Anyone can make the kernel or make dump kernel from your phone put it to somewhere. I tried to make the kernel, but my kernel can not run android because there is no kernel header. Header that makes flashtool unsuitable.
[General Questions and Answers] Soulman2017:
Kernel

Hi garikay can u upload the Zimage so I can see if I can peace the kernel together please thanks
[General Questions and Answers] garikay:
Soulman2017 Look pm. I will not give not working material in open access. I gave it to you for testing. it is not necessary to give open access. For all I give is that working : ramdisk stock and modified, in *.img file and unpacked. Link to file: https://drive.google.com/file/d/0B7NFxP6TLdXCVXZ6SHc3ekpxWjg/view?usp=sharing You need to make zImage from open source by Sony Dev. or unpack boot.sin using flashtool and unpack obtained boot.elf using zip archiver . You will receive a two file - 0 and 1. 0 - your kernel, rename it to zImage. You get exactly what and when compiled from open source. What I tried - get wrong zImage. I got it when I tried to unpack the boot.img using AndImgTool. Other normal kernel unpacked without errors. Made of open source or firmware zImage integrated to boot.img make a mistake.
[General Questions and Answers] drevel123:
Does anyone know where to download the official firmware for the Sony Xperia E5 (f3311)? I need to reflash it, but I can't find anything on Google :(
[General Questions and Answers] meistr91:
Xperiafirm, download flashtool by androxyde for windows, install it, and then u will be able to access xperiafirm there u will easaly download the right software for you. It will download by different format, but flashtool will convert those files to .FTF
[General Questions and Answers] drevel123:
Thank you very much! I have to reflash the firmware for a friend, because it isn't possible to use the sim card any more after the latest update. The factory reset did not help, this is my last hope. Did anyone experience similar problems?
[General Questions and Answers] garikay:
Such problems arise when cleared imei. Check whether it is in place?
[General Questions and Answers] Juako:
Hello, I have E5 / F3311 unlocked through the Sony code. Even no one has managed a recovery that works well for you can flash SuperSu ?. Also some Custom Rom? Thank you.
[General Questions and Answers] IrvingWash:
I'm sorry for my English. There is source of our phones .108 core on the official site (it appeared recently this month). I know a guy who tried to compile a core from the source, but he failed (says there are errors). I'm wandering if someone on this forum tried the source. The guy also says that he needs someone who knows C (programming language), to help him with solving the errors.
[General Questions and Answers] victhor343:
Need root for Xperia E5 F3313 I want it
[General Questions and Answers] marvinalnashi:
I've managed to get other devices rooted by using a tethered temporary bootable cwm recovery and flashing the supersu.zip from within.

I BOOTED the recovery in adb with boot recovery.img, so flash recovery.img won't work here.

I have checked the current twrp that's made by Jemmini, it has bugs and it doesn't have bootup support.

In other words, if we find a way to boot a recovery without breaking the device after a reboot, we're all good to go and will have root on this phone.

We need a new recovery, unless the problem is coming from enabled dm-verity, if that's the case, we then also need a new kernel.

But to flash the custom kernel we'll probably need a recovery, so I guess someone with a unix based OS can rebuild a recovery from the available sources.
[General Questions and Answers] toinedu27:
Hello,

I'm working on macOs (I think that's unix based), could you explain to me what I need to do to build a recovery and which sources I need to use ?

I hope I will can help you ;)
[General Questions and Answers] pottu221:
i made zimage from open source im going to try this out and let you hear what happened :D
[General Questions and Answers] pottu221:
only bootloop

so i made the zimage and created a boot.img and now i just got bootloop. i think that headers are not good. and i dont know how to copy them. some help would be nice :D
[General Questions and Answers] pottu221:
now even pasted header from kernel to image and still bootloop. i think that something is wrong with the ramdisk but im gonna look at it other day
[General Questions and Answers] pottu221:
i dont know how to compile the kernel right way :(
[General Questions and Answers] pottu221:
Has anyone tried this?

Has anyone tried this?

https://mobile.twitter.com/srsroot/status/794245596555182081
[General Questions and Answers] marvinalnashi:
Yeah it's malware, and when it said successfully rooted I still couldn't gain system r/w access with the 8root method.

No luck yet.

By the way I found the old recovery image for the f3311, I'll send it to you soon.
[General Questions and Answers] pottu221:
Okay. Thanks?
[General Questions and Answers] garikay:
No on Sony Development good source codes. Without having them you can not make a working kernel.
[General Questions and Answers] toinedu27:
I remember that : to root an old sony device, I need to use the root of another sony smartphone.Could we use a root method like the one of the sony XA ? (There are tutorials)

Would it be dangerous to use the recovery of other device??
[General Questions and Answers] marvinalnashi:
As recoveries are less device-specific than roms, you should be able to use the recovery of an other device, but it must be based on the same chipset.

Ours is a Mediatek 6735, sometimes using a different recovery and sometimes it won't.

I've tried a twrp of an Lg device with mtk6735 and it failed to boot. Your best bet would be to try to port the recovery of the lg k10 to our f3311, but you must add boot support to it.

In that way we can boot the recovery without the need to flash it, and then root it using a zip file.

I booted a cwm recovery on my tablet and managed to root it in exactly this way.
[General Questions and Answers] ch3mn3y:
[MENTION=5938145]mrmarvin_16[/MENTION]

I think it was tested few pages before, but there is need of kernel which will be able to boot the Recovery.
[General Questions and Answers] IrvingWash:
So, is there any chance the phone will be rootable? Is it a matter of time (maybe Sony will post something on their site, dunno, I am an absolute noob here) or we need a hero?
[General Questions and Answers] ch3mn3y:
[MENTION=8098883]IrvingWash[/MENTION]

Sony doesn't want us to root our devices, but buy one better and more expensive, so don't count on them.

Hero is who is needed here.
[General Questions and Answers] DrZener:
Hi all, I tried to patch boot.img to disable dm-verify, but now i'm in bootloop.

I unpacked the kernel.elf from xperifirm, patched fstab and packed boot.img, but it doesn't work. Why?
[General Questions and Answers] ch3mn3y:
[MENTION=8094126]DrZener[/MENTION]

Aren't there any already made ftf's?

I have some here (all (?) generic and branded for Polish carriers): http://www.xperiasite.pl/forum/349-xperia-e5e5-dual/
[General Questions and Answers] DrZener:
Dunno, but i succeded making my own ftf from xperifirm + sony flashtool (latest version needed).

I built it for my italian F3311 (37.0.A.1.151).

Anyway boot imgs made with mkbootimg form kernel.elf (even without any patches) fail to boot. Faulty ramdisk?
[General Questions and Answers] garikay:
You can not use method XA. Because you do not have a modified kernel. And the recovery for your device should be done on the basis of the kernel.
[General Questions and Answers] DrZener:
What's the XA method? I used the original kernel of the F3311, dumped from official .sin. I only modified the fstab in the ramdisk.

What do you mean with "modified kernel"? The zImage can be modified as far as the kernel source is available (and it is).
[General Questions and Answers] rrvuhpg:
Hi all, I'm the author of the root for XA and XA ultra devices, [MENTION=6405745]pottu221[/MENTION] asked me to help you to root the E5.

First of all I have a bad news, you can't build the required zImage because of some problems in the sources related to missing dependencies in it.

As some of you know the root can't be done without it, you can't use the stock one.

For others I will quickly explain the big steps, after building the zImage you have to edit the ramdisk, find all headers and the cmd line to repack the boot.img (you can find them on similar devices)

After this you can boot to Android but you can't root easily, without a working recovery you have to include Magisk or SuperSu in the boot manually or with kitchen tools. To have a working recovery and have the possibility to flash zip packages the easy way is to port it from a device with the same processor or very similar.

For now you have to ask Sony to fix errors in the kernel sources (and respect GPL rules), they must do it! I don't have this device so my explanations are the only help that I can offer to you. If you have any questions you can ask me in private message, good luck ☺️
[General Questions and Answers] rrvuhpg:
OK I found the error, don't use the compilers from 156 kernel sources. Almost all files in /bin folders are missing, use compilers from 108 sources.

If someone can send me the boot.sin I will try to edit the ramdisk for you :)
[General Questions and Answers] marvinalnashi:
I have different boot.sin files on my pc.

From which firmware do you need it?

I assume you're going to need the 108 boot.sin as you're using the 108 sources :p

I'll upload it soon.

The link to the twrp recovery that was posted on 4pda isn't working anymore, so I re-uploaded it.

Here's the working twrp recovery for the E5: https://drive.google.com/file/d/0BzYsyVWYcCU8OElOT3U4blltZTQ/view?usp=drivesdk

I'll upload any other files that are required for building the kernel if necessary.
[General Questions and Answers] victhor343:
Can find method root for Xperia E5? More users want do this!
[General Questions and Answers] rrvuhpg:
I'm working in PM with [MENTION=8094126]DrZener[/MENTION] to build a correct boot. There is no root method for E5, I use my experience on the XA. The theory is the same for almost all new devices but need to be adapted on each devices. I use the last 156 sources, I just use the compiler from 108. After a first try I can say that the stock headers/offsets doesn't work. Thank you for the files they will probably be useful :) , porting the recovery will be the next step.
[General Questions and Answers] rrvuhpg:
Here for you the so waited boot: https://mega.nz/#!l8RllawL!pfEakPhhnIItFUyxtYGtVbj_agjeXV3JKJ_h3PVrDjk

You can use it with the recovery posted by [MENTION=5938145]mrmarvin_16[/MENTION]. https://drive.google.com/file/d/0BzYsyVWYcCU8OElOT3U4blltZTQ/view?usp=drivesdk

The boot is based on 37.0.A.2.156 firmware, I recommend to update your firmware to it. If you don't find your customization you can flash from an other without problem, there is only very few differences between them.

For a step by step guide you can use my root guide for XA with boot/recovery files given above (don't use boot/recovery for XA/Ultra) :

https://xdaforums.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3430170

You can use directly Magisk Manager to root without using SuperSu (recommended). Big thanks to [MENTION=8094126]DrZener[/MENTION] for tests :)
[General Questions and Answers] marvinalnashi:
I'll test and report immediately with the results.

So first I'll flash the boot.img and then the recovery?

And first of all I'll download magisk from google play I suppose?

Great work!
[General Questions and Answers] rrvuhpg:
Yes, you step order is good ☺️. You will have to flash the downloaded zip from Magisk Manager at last step.

I recommend to wipe your Data partition in TWRP to remove encryption and have the possibility to mount and make nandroid backup in TWRP, backup your personal data before wipe it!
[General Questions and Answers] marvinalnashi:
Congratulations! We have succesfully managed to gain root access on the Sony Xperia E5!

I used adb and fastboot to get things done and I can confirm that this method has worked.

Thanks to everyone who was involved in making this possible.
[General Questions and Answers] Axeman1337:
please, if you don't mind, could you write the steps clear to flash the e5 it would really help me alot! thanks
[General Questions and Answers] ch3mn3y:
[MENTION=8177959]Axeman1337[/MENTION]

Best way?

1. Flash stock 37.0.A.2.156.

2. Unlock Bootloader.

3. Flash kernel using fastboot.

4. Flash recovery using fastboot.

5. Download MAGISK .zip.

6. Copy it onto Your device.

7. Boot into recovery

8. Format data partition.

9. Flash MAGISK in recovery.

10. Wipe cache and Dalvik/ART.

11. Reboot.
[General Questions and Answers] marvinalnashi:
Just follow the guide of the Xperia XA thread.

I've been testing this for a while now and I must say that the app lucky patcher doesn't detect root using magisk, but works fine with supersu, so I recommend everyone to use supersu instead of magisk.

There are other apps that have the same issue with magisk, so I'm going to stick to supersu for now.
[General Questions and Answers] pottu221:
Now when have the root acces and twrp. Should we start porting cyanogenmod to this device?
[General Questions and Answers] marvinalnashi:
Well I'd say LineageOS cause that's the new cm ;)

But I don't have a working linux machine here, if you or anyone else has one they could give it a shot.
[General Questions and Answers] pottu221:
I'll give a shot ?
[General Questions and Answers] Yahari:
Can you provide me the specific files to root you if it's not too much hassle?

:)
[General Questions and Answers] toinedu27:
Thanks a lot guys that worked for me. :)
[General Questions and Answers] marvinalnashi:
I've written a guide to clarify things up.

I hope it's helpful for you. :)

https://xdaforums.com/android/development/root-sony-xperia-e5-f3311-t3584813
[General Questions and Answers] jan.zogmund:
Happy man.

Thank you for all fantastic work guys :)
[General Questions and Answers] IrvingWash:
Thank you guys all! Since I am a noob, I'm gonna wait when someone makes a rooting guide for dummies. And for Android 7 ROMs!

---------- Post added at 09:43 PM ---------- Previous post was at 09:31 PM ----------

Can I please use your instructions to translate in Russian and post on a forum? I won't claim any credits and will mention your name :3
[General Questions and Answers] IrvingWash:
Now I'm having issues when I'm trying to unlock bootloader (via official site). I've done everything as the page states, replaced fastboot driver in sdk folder, but when I'm updating the driver in Devices and printers menu, my PC shows me errors (something about hash). Could please someone help?

I think the problem might be in .Inf file, the page whit unlocking instructions for some reason links to archive dated 2014.
[General Questions and Answers] marvinalnashi:
Of course, as long as you give me credits :)

---------- Post added at 10:14 AM ---------- Previous post was at 10:09 AM ----------

Replacing the fastboot drivers in fastboot folder? I think you've been looking on the wrong site mate.

I'd delete everything and start all over. There's a thread on xda about the minimalistic adb+fastboot drivers, use that installer and please don't involve android sdk with it, I didn't use it and however you can use it too, but I won't recommend it.

Just install the adb+fastboot from that thread and you'll be fine.

The exclamation mark should be gone in device manager after doing that.
[General Questions and Answers] rrvuhpg:
Hi, didn't you forgot to give me credits for my work in your guide ??
[General Questions and Answers] marvinalnashi:
Oh yeah my bad :D

I'll add them in a moment

By the way, I found out your kernel doesn't support changing the se-linux mode.

Is there a way to enable it or do we need to modify the kernel itself again?

Because of this, v4a shows status abnormal and unsupported.

Thanks again
[General Questions and Answers] rrvuhpg:
Changing se-linux to permissive is very bad for security but you can unpack the boot and edit the "cmd line" to disable it. To have Viper4Android in enforcing mode you can try to use it from Magisk Manager module or try to use Viper4Arise flashable zip.
[General Questions and Answers] marvinalnashi:
Thanks, I tried both of them.

Magisk crashes when downloading any module, it just corrupts the file it's downloading and then it crashes.

The viper4arise zip didn't work either, I tested both aroma and non-aroma zips, when I flash them it sticks at the 'starting apps' screen, even after a reboot.

So my first guess is it's something kernel related, at least that's what's written on the v4a troubleshooting page.
[General Questions and Answers] rrvuhpg:
I can't try myself but it can be good to see what happens with logcat.

The kernel used is compiled from sources without any modifications in the code.

You tried to use "compatible mode" in V4A, reboot and play with "master gain" to see if enabled (you can't see the driver status)? At the beginning it was the way to use it on Xperia XA.
[General Questions and Answers] marvinalnashi:
I've tried it, but without luck.

Even in compatible mode and using matter gain didn't do anything.

It seems like we'll have to wait for a rom like lineageOS to be built for this device.
[General Questions and Answers] cosim:
Hello Team.

I am a new one here, sorry if my question was already discussed.

I have a f3311 locked for Vodafone.

In my service menu the such statement exist:

Bootloader Unlock Allowed: No

Tried to unlock using the official methods from Sony and got such error message:

FAILED (remote: Command not allowed)

finished. total time: 0.006s

(No surprises here)

Is there are any way me to have my phone rooted(I don't care about the sim lock at this time)?
[General Questions and Answers] ch3mn3y:
[MENTION=1939540]cosim[/MENTION]

Not using official way. Probably BOX is the only way to unlock sim and bootloader. And as there is no other way to use this method to root the device, as long as You have locked bootloader You may not root it.
[General Questions and Answers] marvinalnashi:
Mine was vodafone locked too, but I simply used a different firmware package, grabbed from Xperifirm, and flashed with flashtool.

Exclude everything that's in the 'ta' section and you're good to go.

Also check your drivers again, you might have the wrong ones installed. [MENTION=4254806]ch3mn3y[/MENTION], every E5 is rootable and sim locks aren't involved in its' compatibility.

Good luck.
[General Questions and Answers] ch3mn3y:
[MENTION=5938145]mrmarvin_16[/MENTION]

I knew that Orange stopped simlockin and fastboot locking their devices.

However it's first time when I hear that flashing different firmware makes it unlockable. That's why I didn't write about it and am not convinces. But if it works for it may be doable.
[General Questions and Answers] pottu221:
Hello make sure that you have oem unlocking allowed from your phone developer settings :)
[General Questions and Answers] IrvingWash:
Any news about custom ROMs?
[General Questions and Answers] IrvingWash:
I suddenly got a mic problem. It doesn't work when I'm recording or speaking with someone, but if I turn on the speaker function (I'm not sure how it's called in English version, the thing that allows to produce sound from the big speaker) mic works. What is it? I've already done a hard reset. Didn't help.
[General Questions and Answers] toinedu27:
I already had this problem on one of the first system version but that was solved with a system update ^^
[General Questions and Answers] IrvingWash:
Thank you, but I have installed the latest update for my region. Hopefully the .156 could help, I'll try today.
[General Questions and Answers] marvinalnashi:
Yeah I've been having the same problem, it indeed got fixed in build .156. I would also recommend you to use this build to root your phone, build .108 had a few problems.
[General Questions and Answers] IrvingWash:
I'm using the latest flashtool, trying to compile a ftf of 156, but there is no F3311 in the device selector window, actually the device selector is blank. Any help? I'm sorry for flooding this thread.
[General Questions and Answers] IrvingWash:
The devices folder in users/pcname/.flashtool/ is empty too. I think I need to manually add there drivers for E5, I downloaded them from here , placed in the folder. Nothing changed.

Update:

Downladed .156 using built in flashtool xperiafirm (flashtool automatically converted it in ftf), now, when I'm trying to flash it, the program doesn't see the file. I else tried to move the ftf in another folder, but problem remains.