Develop Bugs

official discussion thread for LineageOS 14.1

Hello everybody, here our official discussion thread and off topic for our beloved Xperia m.
Good luck for every one [emoji6] [emoji122]
You can download it from here
https://download.lineageos.org/nicki
You can see changelogs here,
https://www.cmxlog.com/14.1/nicki/#lineage-14.1-20170131-nightly-nicki-signed.zip

kh34d said:
Hello everybody, here our official discussion thread and off topic for our beloved Xperia m.
Good luck for every one [emoji6] [emoji122]
You can download it from here
https://download.lineageos.org/nicki
You can see changelogs here,
https://www.cmxlog.com/14.1/nicki/#lineage-14.1-20170131-nightly-nicki-signed.zip
Click to expand...
Click to collapse
Hi brother! Can you help me get the root functionality and recovery back on this device? I was so excited before flashing it. But after flashing, I've lost the recovery and there's no root too. It seems just same as the old CyanogenMod 14.1. Nothing is changed. [I can't flash stock FTF again, 'cause I don't have my laptop with me.]

mayanxoni said:
Hi brother! Can you help me get the root functionality and recovery back on this device? I was so excited before flashing it. But after flashing, I've lost the recovery and there's no root too. It seems just same as the old CyanogenMod 14.1. Nothing is changed. [I can't flash stock FTF again, 'cause I don't have my laptop with me.]
Click to expand...
Click to collapse
Hi.
1. Flash boot.img from zip
2. Boot into recovery
3. Flash TWRP 2.8.6.0 "link: https://forum.xda-developers.com/xperia-m/development/recovery-cwm-twrp-recoveries-custom-roms-t3016507" via recovery
4. Reboot and go again into recovery
5. Flash SuperSU-v2.79 -- this make a root
6. Reboot
..can be ?

olibub said:
Hi.
1. Flash boot.img from zip
2. Boot into recovery
3. Flash TWRP 2.8.6.0 "link: https://forum.xda-developers.com/xperia-m/development/recovery-cwm-twrp-recoveries-custom-roms-t3016507" via recovery
4. Reboot and go again into recovery
5. Flash SuperSU-v2.79 -- this make a root
6. Reboot
..can be ?
Click to expand...
Click to collapse
Are you saying that there is no root without Super SU??
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
Has anyone tried that ROM which is released on 31/01/2017

Prem Chowdhary said:
Are you saying that there is no root without Super SU??
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
Has anyone tried that ROM which is released on 31/01/2017
Click to expand...
Click to collapse
maybe are any different techniques, but this is the fastest method how to get root, only flash this .zip ..i think that easiest way doesn't exist .. and if you want delete a root, on google play exist app from chainfire to remove
good luck ..

mayanxoni said:
Hi brother! Can you help me get the root functionality and recovery back on this device? I was so excited before flashing it. But after flashing, I've lost the recovery and there's no root too. It seems just same as the old CyanogenMod 14.1. Nothing is changed. [I can't flash stock FTF again, 'cause I don't have my laptop with me.]
Click to expand...
Click to collapse
Hi, I think you must wipe everything and begin from stock rom. [emoji20]
Did you tried this add-on for root??
https://download.lineageos.org/extras

kh34d said:
Hi, I think you must wipe everything and begin from stock rom. [emoji20]
Did you tried this add-on for root??
https://download.lineageos.org/extras
Click to expand...
Click to collapse
The root addons works fine. Is the supersu still causing the bootloop for dual sim.
Also anyone know the way to retain twrp recovery after flashing lineage os

SONY-Logo is back and everything works fine with todays nightly!!! YEAH!!! Thanks to the developer!

i have flashed latest build of lineage os end got error:"detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" while flashing this rom. Also I have cm14.1 on sd card that works fine, but can't flash lineage os.

Keyursoni said:
i have flashed latest build of lineage os end got error:"detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" while flashing this rom. Also I have cm14.1 on sd card that works fine, but can't flash lineage os.
Click to expand...
Click to collapse
flashing takes very long! did you wait till it finished? Which recovery did you use?

emc02 said:
flashing takes very long! did you wait till it finished? Which recovery did you use?
Click to expand...
Click to collapse
I m using twrp recovery.

olibub said:
maybe are any different techniques, but this is the fastest method how to get root, only flash this .zip ..i think that easiest way doesn't exist .. and if you want delete a root, on google play exist app from chainfire to remove
good luck ..
Click to expand...
Click to collapse
What I ment to say is, "dosent it have root as it was in CM 14.1? "

LineageOS 20170131 Nightly
I just did a quick install of LineageOS 20170131 Nightly.
There is no default system su i.e no root access.
There is a BASIC Cyanogenmod Recovery with no functionality, but it removes my original TWRP 3.0.2 recovery.
I then thought I'd just reinstall TWRP 3.0.2 by Fastboot and see if I could reboot back into LineageOS 20170131 Nightly...No.
I just re-installed a AOSP 7.1 build until I've had a bit more of a think.
SO.... I then thought I'd better have a look/read and see what other people are doing....
Using LineageOS 20170131 Nightly seemed stable and usable for the short time I was using it. WiFi all OK.
No problems installing it.
It does take 11½ minutes (i.e. a VERY long time) for the first initial boot to load.
The LineageOS startup animation logo does appear quickly on the first boot (Less than a minute).
You'll be staring at the circle expanding/contracting on the arc for a VERY long time though.
So leave it 15minutes+ before you consider pulling the battery.
Anyway, that's my show and tell.
Update - Root access is available when you install the su.zip at the initial build (LineageOS extras)
You may have problems installing SuperSU if that's your thing, as it may be a restricted SU built into the LineageOS menu only.
SU options are inside developer menu which is activated by a few taps on build number in About menu.
I still haven't worked out how to set TWRP as default recovery.

Prem Chowdhary said:
What I ment to say is, "dosent it have root as it was in CM 14.1? "
Click to expand...
Click to collapse
..if i understand corretly what you say, :this depends on developer.. to cm13 was always root but from cm developers "not custom developers" except AOSP etc. "NOT" ..for example on cm 14 should be a root

I found here some guide for installation, may help you.
https://forum.xda-developers.com/showthread.php?t=3546041

Android 7.1.1 LineageOS potential standby over 8days
Haven't really done much with my C1905 running Android 7.1.1 LineageOS but over 8 days idle standby is pretty good start.
{
"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"
}
That's with no Location/GPS, WiFi always on, no mobile data and 100% telephony signal.

I finally installed lineageos on my xperia m , the latest build 20170207. Before lineageos it was running on Cm-14.1.
So far everything works all right. Recovery twrp 3020 works great.
I did clean install, first boot took 7-8 min, flashed su (arm) and that is it.

Antimon1 said:
I finally installed lineageos on my xperia m , the latest build 20170207. Before lineageos it was running on Cm-14.1.
So far everything works all right. Recovery twrp 3020 works great.
I did clean install, first boot took 7-8 min, flashed su (arm) and that is it.
Click to expand...
Click to collapse
Is there any difference than cm14.1? Memory management and performance.

I am also curious to know as I am not happy with CM 14.1 memory management.

Keyursoni said:
Is there any difference than cm14.1? Memory management and performance.
Click to expand...
Click to collapse
It is very similiar to cm14.1. But it seems to me that it is a bit faster, I have a little bit more free ram and battery life is better. Boot is faster too and LineageOS is very stable, at least for now.

Which is best stable ROM for Yureka with good battery backup?

I recently upgraded to YUOS marshmallow from cyanagon Lollipop. But battery backup is very bad. Can someone please tell me which one is best rom with no battery issues. camera is also very bad in yuos.
I did force stop to media storage app, and since then the battery is draining very fast, even after factory reset and upgrading to OS.
What could be the reason for that? Could system or partition be corrupted which is not fixed after os upgrade also?

vishalhbti said:
I recently upgraded to YUOS marshmallow from cyanagon Lollipop. But battery backup is very bad. Can someone please tell me which one is best rom with no battery issues. camera is also very bad in yuos.
I did force stop to media storage app, and since then the battery is draining very fast, even after factory reset and upgrading to OS.
What could be the reason for that? Could system or partition be corrupted which is not fixed after os upgrade also?
Click to expand...
Click to collapse
Same was the problem with my phone bro. I downloaded adb files to my PC. Then flashed twrp. With TWRP I had installed Resurrection Remix (Android 7.1) OS and Gapps(micro). Also flashed modem files for volte support. Now its working fine.
Everything with God's blessing, from YouTube I had learned step by step and now peacefully settled. Kindly take the risk of learning. Thank You. Peace be to you. God bless

ajaysp18 said:
Same was the problem with my phone bro. I downloaded adb files to my PC. Then flashed twrp. With TWRP I had installed Resurrection Remix (Android 7.1) OS and Gapps(micro). Also flashed modem files for volte support. Now its working fine.
Everything with God's blessing, from YouTube I had learned step by step and now peacefully settled. Kindly take the risk of learning. Thank You. Peace be to you. God bless
Click to expand...
Click to collapse
Can you share the url of that post from which you followed?

vishalhbti said:
Can you share the url of that post from which you followed?
Click to expand...
Click to collapse
Sure bro..
(Twrp installation and rooting)
Kindly download the latest versions, the versions provided in this vdo description are older. Rename it in coding. )
(Android 7.1) Resurrection Remix OS installation
Volte Modem file
All the Best
---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------
ajaysp18 said:
Sure bro..
(Twrp installation and rooting)
Kindly download the latest versions, the versions provided in this vdo description are older. Rename it in coding. )
(Android 7.1) Resurrection Remix OS installation
Volte Modem file
All the Best
Click to expand...
Click to collapse
If your screen goes black while answering calls.. Please follow this vdo after the installation of RR and GApps
TY

you can try the lineage unofficial build also

Upgrade from AEX 4.6 to RR 6.0 (kinda lost) ?

Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,

Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP

sixth.pr1m3 said:
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP
Click to expand...
Click to collapse
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
EDIT: Alright, I installed "Arnova's Pixel2Mod v6" and I now have a working camera. Do not mind my question. I also noticed that you posted the link (on another thread) where I found the Camera mod, so thanks again for your help!

Sinero said:
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
Click to expand...
Click to collapse
Using GCam? HDR option should be working, try the recommended one's from here: https://www.celsoazevedo.com/files/android/google-camera/
Slow motion is not working. If you have dark video issue, use OnePlus 5T Cam.

Thanks again for that link, seems like I edited my last post while you answered !
Here is a little feedback after ten days of usage :
My camera started acting up : usually when going through the camera's gallery the application will crash. I will try another Gcam.
I also noticed that my calls are not working. I can dial someone but when they pick up the call we cannot hear each-other. Does anyone have experienced this kind of situation ?
Everything else is working smoothly, better than under AEX 4.6, sadly with those two main problems I may have to try something else.

Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
For offline charging flash at beast kernal

Super slow GPS on mi Max 3

Hi guys,
I have the mi Max 3 unlocked, with TWRP and rooted.
I have been running it with RevOS and now with GSI Havoc...
But there seems to be a real problem with the GPS ! It's super slow...
A fix takes about 30 seconds sometimes even more (in the same location, the Honor Note 10 fixes in 3/4 seconds).
And while I traval => "GPS connection lost" happens quite often and it also happens that I get "Searching for network".
Is there a "radio.img" or something like that that I may have to flash to improve things ?
Do you guys have the same when using GPS (like Waze) ?
Or is my device defective ? Should I try to reflash the global ROM for this ?
Thanks for your answers.

I use Xiaomi.EU Rom 8.11.15 (last Oreo updated), used Waze first time this morning and locked in incredibly fast.
Maybe down to the OS you are on?

AsadP2013 said:
I use Xiaomi.EU Rom 8.11.15 (last Oreo updated), used Waze first time this morning and locked in incredibly fast.
Maybe down to the OS you are on?
Click to expand...
Click to collapse
Hi,
Thanks for your answer.
Maybe the OS. But now I am using Havoc OS Pie and I have the same problem Super slow fix : like 30 seconds and up to 1 or 2 minutes.
Will try to reinstall original MIUI stock but I fear to get a device with ARB protection (which I would like to avoid).
Regards.

NexusPenguin said:
Hi,
Thanks for your answer.
Maybe the OS. But now I am using Havoc OS Pie and I have the same problem Super slow fix : like 30 seconds and up to 1 or 2 minutes.
Will try to reinstall original MIUI stock but I fear to get a device with ARB protection (which I would like to avoid).
Regards.
Click to expand...
Click to collapse
What version are you on?
If you are MIUI 10, don't go below MIUI 10.
If you are on MIUI 9, like I was out of the box, 9.6.12, you cannot go down. anything above 9.6.8 has ARB really.
I got soft locked and I had to use MiFlash to restore Global ROM.

...or you just clean up the miui from all the ARB related sh*t before flashing it...

Hi guys,
Thanks for your answers...
Definitely ROM related.
I restored stock MIUI 9.8.6.0 (last official with no ARB) and Xiaomi.eu 8/8/9 (latest non official with no ARB) and with those, I got a GPS fix within seconds...
And that quick fix is reproductible...
So : there goes RevOS, which is a pity : it was superb and with lot of added customizations abilities...
Regards.

nijel8 said:
...or you just clean up the miui from all the ARB related sh*t before flashing it...
Click to expand...
Click to collapse
Hi,
Interesting...
How do you do that ?
Regards.
NexusPenguin

NexusPenguin said:
Hi,
Interesting...
How do you do that ?
Regards.
NexusPenguin
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=78248423&postcount=9

nijel8 said:
https://forum.xda-developers.com/showpost.php?p=78248423&postcount=9
Click to expand...
Click to collapse
Hi,
Thanks for the link.
But I must say that I am a little anxious about that
First : it is unclear if I have to LEAVE the listed files in the FW-update folder or if I have to take ERASE those ;
Second : is it confirmed that if I do that, I won't have ARB on my device ? Because it seems that the author is just "speculating" about this and asks for confirmation...
So if you could provide a little more details, I'd be a taker
Regards.

Those are the files you should flash. All others not listed you delete along with the lines in updater-script/flash-all.bat. Haven't tested it myself b/c I don't care about MIUI and I only flash boot, system and vendor to test my stuff I work on. But later on I will have to test it b/c I will need vendor and firmware for my next project. So although not tested these files should be ARB safe, the rest of them removed are bootloader related where ARB resides. But with anything Xiaomi I can't be 100% sure until test it personally. What I can asure you is no ARB if you flash boot, system and vendor only...

[UNITY] Various Fixes for the Moto G5/G5S [9+]

HUGE thanks to @giri45 for actually providing the fix!
What's this? ​
A Unity installer ensures that you can use this module with any kind of root solution (as long as it supports init.d)! If you have Magisk, flash the module through the Magisk Manager, but if you don't have Magisk, just flash the module through TWRP. When you want to uninstall the module, flash it again in Magisk Manager or TWRP.
As for the module itself, it provides a fix for LiveDisplay/Night Light on the Moto G5/G5S for anyone running an AOSP-based ROM running Android 9 or higher, and enables Camera2 API + EIS if you wish so.
Do NOT attempt to install this on other devices, or ROMs based on Android <9! Device and Android version checks have been applied to make sure this module will not install on incompatible devices. This module assumes that you are using the latest stock Oreo firmware (including bootloader, GPT and etc.)! Do not report issues if you are not on the latest firmware.
Tested ROMs:
Havoc OS 2.2
Pixel Experience 9.0
AOSPExtended 6.3
crDroid 5.0
Known issues:
Fix doesn't work on Nougat firmware. You must have fully flashed the stock ROM/flashed it via OTA, for this fix to work.
Downloads:
Download from Magisk Repo.​
Flash via Magisk Manager or TWRP. Make sure you have a root solution which supports init.d!

Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..

Ænimal said:
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Click to expand...
Click to collapse
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...

JarlPenguin said:
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
Click to expand...
Click to collapse
Deleted

PE 9.0LOG is attached

@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx

Ænimal said:
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Click to expand...
Click to collapse
It's an internal build. You can test it out here: https://t.me/montanadevelopment

JarlPenguin said:
It's an internal build. You can test it out here: https://t.me/montanadevelopment
Click to expand...
Click to collapse
I'm running this build now and tried the fix but to no avail, still (xt1794)

Ænimal said:
I'm running this build now and tried the fix but to no avail, still (xt1794)
Click to expand...
Click to collapse
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?

JarlPenguin said:
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
Click to expand...
Click to collapse
Nougat firmware and Oreo baseband, screen is original. Do you think that partition table is the problem?

Ænimal said:
Nougat firmware and Oreo baseband. Do you think that partition table is the problem?
Click to expand...
Click to collapse
Okay, I think I have found the problem now. What have you not upgraded?

JarlPenguin said:
Okay, I think I have found the problem now. What have you not upgraded?
Click to expand...
Click to collapse
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts

Ænimal said:
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Click to expand...
Click to collapse
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.

JarlPenguin said:
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
Click to expand...
Click to collapse
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev

Ænimal said:
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Click to expand...
Click to collapse
That's weird... One thing I know that is that this fix doesn't work on Nougat firmware.

Working flawlessly on crDroid 9.
Thank you devs!

I have installed the mod with magisk and not working on my device with Pixel Experience 9.0

Arn'oh said:
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Click to expand...
Click to collapse
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM

zahidm said:
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
Click to expand...
Click to collapse
I had updated to Oreo official beta test with fastboot commands

Arn'oh said:
I had updated to Oreo official beta test with fastboot commands
Click to expand...
Click to collapse
Did you flash everything? Try fully flashing Stock Oreo via Fastboot and then install TWRP, custom ROM and this fix.