[ROM][UNOFFICIAL][10][Q]LineageOS 17.1 for z5c (suzuran)

[casouzaj]

Hey, how can I root this one?
The ROM is just perfect, but I really want to root it
I´ve tried super su and magisk but I cant

I run this ROM since it was released. Magisk has always worked for me. I used the stable v21.4 for a long time. I tried the recent Canary v22 and it works, as well. The v21.4 I first installed by TWRP, and all subsequent versions by Magisk Manager Direct install (and reboot).

 

[Berni-0815]

how can I root this one?

Only Magisk is working. I'm using "Magisk-v21-4".

 

[erickcersosa]

I run this ROM since it was released. Magisk has always worked for me. I used the stable v21.4 for a long time. I tried the recent Canary v22 and it works, as well. The v21.4 I first installed by TWRP, and all subsequent versions by Magisk Manager Direct install (and reboot).

Can u help to do it please, or guide me to do it?

 

[casouzaj]

Can u help to do it please, or guide me to do it?

Download Magisk's zip file of the Canary release from https://github.com/topjohnwu/Magisk, copy it to anywhere in your phone. Boot to TWRP, tap on Install > Select storage > choose the location where the Magisk zip file was copied to > tap on the file > slide the bottom to install > Reboot to system.

When your phone is up and running, launch Magisk, tap on the gear icon (on the top) and turn on the Magisk hide switch. Tap on Systemless hosts. Tap also on Hide Magisk Manager > choose any name > Reboot. When your phone is up again, launch the app whose name you changed. Tap on the shield icon on the bottom > Magisk hide and turn on the keys for apps which would accuse your phone of being rooted, like banking and working apps.

 

[erickcersosa]

Download Magisk's zip file of the Canary release from https://github.com/topjohnwu/Magisk, copy it to anywhere in your phone. Boot to TWRP, tap on Install > Select storage > choose the location where the Magisk zip file was copied to > tap on the file > slide the bottom to install > Reboot to system.

When your phone is up and running, launch Magisk, tap on the gear icon (on the top) and turn on the Magisk hide switch. Tap on Systemless hosts. Tap also on Hide Magisk Manager > choose any name > Reboot. When your phone is up again, launch the app whose name you changed. Tap on the shield icon on the bottom > Magisk hide and turn on the keys for apps which would accuse your phone of being rooted, like banking and working apps.

Thanks. Ill try

 

[florstat]

hi berni, thanks a lot for your tireless efforts, they were the reason why i felt confident enough to get a Z5C.

does anybody have advice on how to reduce the massive echo my call partners experience when loudspeaker is active (both phone and app calls)? without loudspeaker there is a slighter but still noticeable echo. curiously, the problem was the other way round in berni's los14.1. haven't tried 18.1 yet but would be my next option.

cheers from berlin

(E5823 with december build)

You may make a try with this, for me it has worked with los 14.1.

The ECHO issue

During calls the people can hear an echo of themselves. With a slight delay. I have found this suggestion for changing making changes in the mixer_paths.xml.

forum.xda-developers.com

 

[Berni-0815]

You may make a try with this

Please take a look at my answer in the mentioned thread: Klick

 

[plusminus_]

Footej Camera 2 seems to focus fairly well in my very brief test (though I had nothing interesting to take pictures of!)

I also found a thread about a different Q ROM. The idle drain rate seems similar to what has been reported earlier in this thread, around 2.5%/h. I think I have reduced it further, and my phone can now go a whole day between charges again, just about

Can this kernel control the wlan_rx_wake wakelock? Just wondering

 

[TRKARTAL]

@plusminus_ hello, thanks for that new /e/ rom information. i never hear this and its good to know our device have another rom builds.
For blocking kernel wakelocks; i recommend the Boeffla Wakelock Blocker Driver .
Dear @DevelLevel has included that driver into his AospExtended Nougat Rom, XDA Thread:https://forum.xda-developers.com/t/rom-7-1-2-aospextended-v4-6-unofficial-suzuran.3910036/

and the Include Boeffla Wakelock Blocker Driver Commit GitHub link:https://github.com/DevelLevel/android_kernel_sony_msm8994/commits/7.x-aex

Maybe dear @Berni-0815 can include this driver into his rom.

 

[Ermann123]

A bit offtopic:

Is there something existing lie OmniSwitch , that is working on 17.1?
On 14.1 it works flawlessly, but on 17.1 it crashes immediately.

 

[plusminus_]

@plusminus_ hello, thanks for that new /e/ rom information. i never hear this and its good to know our device have another rom builds.
For blocking kernel wakelocks; i recommend the Boeffla Wakelock Blocker Driver .
Dear @DevelLevel has included that driver into his AospExtended Nougat Rom, XDA Thread:https://forum.xda-developers.com/t/rom-7-1-2-aospextended-v4-6-unofficial-suzuran.3910036/

and the Include Boeffla Wakelock Blocker Driver Commit GitHub link:https://github.com/DevelLevel/android_kernel_sony_msm8994/commits/7.x-aex

Maybe dear @Berni-0815 can include this driver into his rom.

Yes, I was quite surprised to see that there was active development going on elsewhere for this little phone! They even mention Berni's ROMs at some point lol

I actually had Boeffla in mind as I have seen it being used against wakelocks such as wlan_rx_wake. I did not know it was 'just' a driver, I thought it was something unique to someone's custom kernel This is... interesting, thank you

 

[Berni-0815]

New version out; see 1st post.

• Android security patch level: 5 March 2021

 

[tarukanav]

Hm got stuck on android animation with latest update

 

[Berni-0815]

I'm testing every version I publish! So I can say that this version is working flawlessly.
You're doing something wrong.
Maybe you should make a clean install?

 

[NeXt3R]

great job Berni-0815 .,,.17.1 i using long time all works fine
,..,you revived this great phone .d

Hm got stuck on android animation with latest update

try extract boot.img from update ,.,.re-flash this BOOT in recovery // or with fastboot
possitible problem is magisk 22.xx up

after "when the boot can be completed"
in magisk 22 - create modded boot ,.,.this flash for ROOT

​

last version tested ,.,still works fine

 

[Berni-0815]

try extract boot.img from update

Normally the flashing procedure overwrites the previously installed boot image. I always had to reflash Magisk after an update.
But maybe that this has been changed in Magisk 22. Try to remove Magisk with this tool before flashing a new ROM.

 

[Ermann123]

New version out; see 1st post.

• Android security patch level: 5 March 2021

Meanwhile on 17.1 with even encryption working (!) , system runs nearly flawlessly.
But the last update crashed the microg configuration, so now every app needs to be un- and reinstalled again to to get registered for GCM. Does anybody know a workaround to avoid this procedure?

 

[Lehil]

Hi!
I encountered an issue using this ROM.
I'm sorry in advance if it had been discussed earlier, I did look for it, but the thread is getting kinda long, so I can't really keep track of it
So for some reason I can't record video footage in any camera app.
(open camera says "the video file could be damaged" and does not save; Footej shows a black screen when I switch to video; the stock camera app simply freezes)
Interestingly enough, other apps like fb Messenger are capable of recording video.
I tried both APIs, and tried reinstalling the camera apps, to no avail.The march patch is here anyway, so I thought I'd ask about a solution, but if it can't be solved, I'll simply punch a clean install.

 

[tntcl]

Wipe everything from within TWRP (Dalvik, Data, Cache, System, Internal) then format data. Flash the original 32.4.A.1.54 firmware and do not perform a .TA recovery from backup. Before booting into system flash recovery. Boot 7.1.1 system and complete basic setup (added from reply below). Boot into recovery and repeat first step: wipe everything followed by a format of data. Flash 18.1, after setup and report back as to the status of the sound issues.

[tl;dr] didn't work, but i couldn't do exactly that

in the last months i either didn't get flashtool.net to work, or i didn't get to mess with my phone at all. so i reverted to sony's EMMA flash tool, which means i got an older firmware and i couldn't exclude .TA recovery. did the rest as instructed (with berni's 3.5.1 TWRP). with 18.1 + nikgapps_core neither phone calls nor camera worked (didn't even go and test anything else), and now on 17.1 these work, but all voip calls (signal, telegram...) still have a massive echo for the other party (speaker) or i'm barely audible (no speaker).

will look into what florstat posted next, dunno when i'll get to it...

 

[VBBoston]

Hm got stuck on android animation with latest update

I have the same issue, wiped everything and formatted data in TWRP, still gets stuck on animation after bootloop. After first boot it goes as far as to Android setup Welcome sign, I press Start, then the circle starts going saying "Just a sec", then reboots and gets stuck on Lineage animation. Also tried with no GAPPS, no Magisk, still the same. Did anyone find a solution?

P.S. Model is E5823.
by the way flashing this https://forum.xda-developers.com/t/rom-11-x-havoc-os-4-2-unofficial-suzuran.4249577/ using the same method boots fine but fingerprint sensor and SafetyNet do not work there so this thread's ROM would be much better