Root E5823 on marshmallow

[rolo143]

Thanks for the reply, i can't stand lollipop anymore so i'll give it a try ! I'll update once done!

If you can't stand lollipop then you won't stand marshmallow either, it's almost the same thing, no big differences.

 

[kevinwu128]

If you can't stand lollipop then you won't stand marshmallow either, it's almost the same thing, no big differences.

The thing I couldn't stand was the lag.. I've done a dirty upgrade and everything is working perfectly with root!

I have some 3rd party apps that used to be able to write to SD card using the patch "SDFix" I now can't get them to write to anywhere on the SD card.. Does anyone know how to fix this?

 

[Helleren]

I only wanted to share the way *I* did it. (because different people mentioned there's no root for Z5C)

I guess it will work with any E5823_32.1.A.* and. it. could also work with other/newer kernels/TWRP/superSU... but I didn't test anything else than this device and this setup. + I know for me it didn't work with TWRP 2.8.7.

Everything seems to be working on the Nordic combined
Dirty flashed boot.img and recovery.img, booted into TWRP and flashed superSU
No problems with Google play store

Thanks for the guide!

 

[DanielMalmgren]

--> Clean install, if not, you'll get Google Play Store and Google Play Service to be forced to close.

Just wondering... could this be simply because there are remains of Lollipop apps still in the phone? Did anyone try to do a dirty install and then afterwards simply flash a MM gapps? Or maybe remove all upgrades to store and services?

I haven't done the upgrade at all yet, thought I'd try to avoid doing the wipe

/Daniel

 

[youvedone]

Just wondering... could this be simply because there are remains of Lollipop apps still in the phone? Did anyone try to do a dirty install and then afterwards simply flash a MM gapps? Or maybe remove all upgrades to store and services?

I haven't done the upgrade at all yet, thought I'd try to avoid doing the wipe

/Daniel

I tried... see my posts around: http://forum.xda-developers.com/z5-...llow-topic-t3299105/post65736733#post65736733

 

[Helleren]

Just wondering... could this be simply because there are remains of Lollipop apps still in the phone? Did anyone try to do a dirty install and then afterwards simply flash a MM gapps? Or maybe remove all upgrades to store and services?

I haven't done the upgrade at all yet, thought I'd try to avoid doing the wipe

/Daniel

nothing happened with Google play when I flashed recovery and kernel...
I did however get those errors when i moved from LP to MM without wipe.... just had to update both apps, then all was good

 

[DanielMalmgren]

I did however get those errors when i moved from LP to MM without wipe.... just had to update both apps, then all was good

Now it's getting interesting... You updated them how?

/Daniel

 

[do_salah]

Can TA be backed up?
Its not fear holding me back. its just... its just... argh (Vegeta) lol

 

[Helleren]

Now it's getting interesting... You updated them how?

/Daniel

Thats a good question! I wasn't paying attention to what exactly happened... i was too thrilled to finally get MM!

I think after a few minutes running MM I got a notification saying google play services had stopped, and i had to update Google play store and services for it to work. when i closed the notification i was automaticly directed to what i think was play store with only option to update Google play services.... This happened 2 or 3 times, but after that i have had no problem

 

[DanielMalmgren]

Thats a good question! I wasn't paying attention to what exactly happened... i was too thrilled to finally get MM!

I think after a few minutes running MM I got a notification saying google play services had stopped, and i had to update Google play store and services for it to work. when i closed the notification i was automaticly directed to what i think was play store with only option to update Google play services.... This happened 2 or 3 times, but after that i have had no problem

That's the way they discovered penicillin, you know... One day they just did something and there it was

I guess the broken play services still has the capability to upgrade itself into something that is not broken then. Guess I'll just have to try it out for myself. Worst thing that could happen would be me being without play store in which case I can just do a factory reset then...

/Daniel

 

[DanielMalmgren]

Ok... Did a dirty upgrade and Play Store seems to work without any problem. I didn't do anything to get it working, it just did

Anyway, I've got another problem. I flashed supersu and it seemed to work. And I can start the supersu app. But the app just says "There is no SU binary installed, and SuperSU cannot install it.". Anyone knows what could cause that? I used the supersu linked in this op, I guess it should be MM compatible?

/Daniel

edit: Tried both 2.65 and 2.68 now with same result.

edit 2: Fixed it. Installed another twrp. I first used the one from androplus (which was downloadable from the same place as the kernel, but now mysteriously gone, maybe because it was broken?), now I used the one in this op. Sorry for deviating from the guide

 

[rolo143]

How can I boot into twrp without actually flashing it to my device? I want to use computer to boot into recovery then flash supersu and thats it. I just want to install supersu in MM. Is this possible? Or do I have to install androplus kernel, twrp and then flash it? I really don't want to mess up with the kernel. :/

edit: i just tried to boot into twrp without flashing it, using fastboot commands but it didn't work, it didn't boot into twrp just got stuck at sony logo. Now I'm curious if it will work if I flash it.

Also.. Has someone tried this method to root a e5803 model? does it work?

EDIT: OMG! I can't believe it!!! I just followed the steps from OP hoping it would work on my E5803 Model and it did!!!! Finally!! I have rooted MM!!! Woohoo!! I'm so excited right now!

 

[rolo143]

Voila!!!

 

[civicsr2cool]

For those who didn't know already: yes, there's a way to root Z5 compact with MM. Bootloader needs to be unlocked.

(1) Install Marshmallow. I did it with flashtool. (I used E5823_32.1.A.1.163_1299-0270_R7C)
--> Clean install, if not, you'll get Google Play Store and Google Play Service to be forced to close.

(2) Install another kernel over here. It's AndroPlus kernel, and I choose the latest version (v20).
--> extract boot.img
-->> (in fastboot mode: power down + press vol up + insert USB) fastboot flash boot boot.img

(3) Install TWRP over here, like found in this threat. It's TWRP 3.0.0
--> rename recovery.img
-->> fastboot flash recovery recovery.img

(4) Flash SuperSU like you can find here. I flashed v2.65

You can reboot, your Z5 compact will be on Android 6.0 with Root Access.

By the way, read this before you try to install Xposed.
It's possible to install Xposed. I used v80-sdk23-arm64.zip (framework to flash) and XposedInstaller_3.0_alpha4.apk as installer.

That xposed part makes little sense to me. What is it trying to fix?

 

[pep086]

HI jenana,
If i follow your instructions and i wanna go back to my Lollipop backup of TWRP, i can flash it on recovery to go back?
i can't wait to try MM, thank youu.

 

[goeland86]

Weird, I'm getting different behavior and root doesn't work for me.
Phone is E5823 flashed with MM Custom CH (where I live)
TWRP sees SD card but not internal storage.
I flash the SuperSU 2.65 linked from first post, and SuperSu app shows up in apps list, but no root access. When I try to open up SuperSu message is "There is no SU binary installed, and SuperSU cannot intall it. This a problem!" (oh really? Hadn't noticed that bit!)

 

[DanielMalmgren]

Weird, I'm getting different behavior and root doesn't work for me.
Phone is E5823 flashed with MM Custom CH (where I live)
TWRP sees SD card but not internal storage.
I flash the SuperSU 2.65 linked from first post, and SuperSu app shows up in apps list, but no root access. When I try to open up SuperSu message is "There is no SU binary installed, and SuperSU cannot intall it. This a problem!" (oh really? Hadn't noticed that bit!)

I recognize both those problems.

First the SD card. It's the same here, I can only reach external SD from twrp. I don't see it as a problem though, as long as some area where I can put files are visible

About the second one... Did you flash the twrp linked in the op? I got exactly that behaviour when I used another twrp (which I downloaded from androplus.org). It seems the supersu didn't flash correctly from that twrp. When using the twrp in this thread everything works perfect for me.

/Daniel

 

[goeland86]

I recognize both those problems.

First the SD card. It's the same here, I can only reach external SD from twrp. I don't see it as a problem though, as long as some area where I can put files are visible

About the second one... Did you flash the twrp linked in the op? I got exactly that behaviour when I used another twrp (which I downloaded from androplus.org). It seems the supersu didn't flash correctly from that twrp. When using the twrp in this thread everything works perfect for me.

/Daniel

I used the twrp 3.0.0 linked in the first post... Will try again to flash a fresh twrp tomorrow.

 

[BlackArtsInc]

So this means that we can get root on Marshmallow without any problems as far as the DRM keys are concerned? It's totally safe to do or not? I was on rooted Z1 Compact but with TA Partition backed up so it felt a bit safer.
N.

Sent from my E5823 using Tapatalk

 

[goeland86]

I used the twrp 3.0.0 linked in the first post... Will try again to flash a fresh twrp tomorrow.

Ok I apparently had flashed the wrong recovery - I'd downloaded twrp 3.0.0 from the same google drive as the kernel image - flashed the recovery from the thread linked in the original post and now it works. Also, using original recovery I have access to both internal and SD storage. :good: