Develop Bugs

Wifi Region code Connectivity problems: A Solution

Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk

arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later

atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.

arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.

atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.

arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.

atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of

arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess

atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL

arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone

atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.

Flashable zip added for new Commotio Rom Nightlies

Any chance to apply the patch to a stock rooted rom?
Thanks

Region Code
Hi can someone fix this file for region code?

nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.

Can someone post the patch for latest cm nightlies?

nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based

nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.

BLN-L24 links have bad key in the Honor 6x Repository thread

Need to rollback, or be advised of any custom ROMS that work..

Try Elite ROM from ROM section. it should work fine.

I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.

BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc

TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.

ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?

Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.

No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.

ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.

Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.

If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?

I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.

Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP

[ROM Choice] Most stable ROM on Moto Z Play

Whats the most stable ROM for the Moto Z play?
I want to flash only once

Stock one.

It's depends.
My favourites:
RR
AOKP
CR
CANDY
DU
AOSIP
DU

i have used all of them and the most stable and best battery life rom for me is lineage 14.1 official.

briankariu said:
Whats the most stable ROM for the Moto Z play?
I want to flash only once
Click to expand...
Click to collapse
RR is dead now ( at least for MZP)
CR is good for now ( 7.1.2 ) , stable and good for daily driver with good customisation options

RR is the best till now

Is there a DU rom for our device?

briankariu said:
Whats the most stable ROM for the Moto Z play?
I want to flash only once
Click to expand...
Click to collapse
I think if you flash just one and not try others you are short changing yourself. At that point you may has well not even unlocked your phone, stay full stock.
Looking to flash just one Rom is like just trying one flavor of ice cream and then deciding all other flavors are not worthy. Do not let someone tell you what is best, try as many as you can, then you tell yourself which is best for you. Each has its own advantages and each has it own flaws only you can say which you like best. As for the word Stable, they are all about the same... Some are more out of date but that does not effect its stability. Try them all and have fun.
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
Kdx10 said:
Is there a DU rom for our device?
Click to expand...
Click to collapse
An Unofficial one which was released back in August.

stock.

Jimi Mack said:
I think if you flash just one and not try others you are short changing yourself. At that point you may has well not even unlocked your phone, stay full stock.
Looking to flash just one Rom is like just trying one flavor of ice cream and then deciding all other flavors are not worthy. Do not let someone tell you what is best, try as many as you can, then you tell yourself which is best for you. Each has its own advantages and each has it own flaws only you can say which you like best. As for the word Stable, they are all about the same... Some are more out of date but that does not effect its stability. Try them all and have fun.
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
An Unofficial one which was released back in August.
Click to expand...
Click to collapse
Is there a safe way to downgrade to MM? I'm in Nougat 7.1.1 with Dec 2017 patch. with dual sim variant. I want to flash MM 6.0 or 6.1 with Nov or Dec 2016 patch.
I know i have to unlock bootloader. What i need a file for MM 6.0/6.1 with Nov.Dec 2016 patch and a link to do a downgrade.
I would appreciate any response.

jeprox said:
Is there a safe way to downgrade to MM? I'm in Nougat 7.1.1 with Dec 2017 patch. with dual sim variant. I want to flash MM 6.0 or 6.1 with Nov or Dec 2016 patch.
I know i have to unlock bootloader. What i need a file for MM 6.0/6.1 with Nov.Dec 2016 patch and a link to do a downgrade.
I would appreciate any response.
Click to expand...
Click to collapse
NEVER try to downgrade => permanently bricked phone.
ie if you're on nougat, DON'T try to go back to MM.

Jimi Mack said:
NEVER try to downgrade => permanently bricked phone.
ie if you're on nougat, DON'T try to go back to MM.
Click to expand...
Click to collapse
I think it would only bricked if i update back again to nougat, right? I dont mind staying in rooted MM than to be uptodate with N which drain battery faster

jeprox said:
I think it would only bricked if i update back again to nougat, right? I dont mind staying in rooted MM than to be uptodate with N which drain battery faster
Click to expand...
Click to collapse
I have heard it both ways - bricked on MM or bricked on return to N. It's your phone. Just realize the chance you are taking.
I have found @AmulyaX 's
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
(7.1.2) to be fantastic on battery life. Much better than MM. It's what I use most of the time these days until Oreo gets sussed.

tiago1966 said:
It's depends.
My favourites:
RR
AOKP
CR
CANDY
DU
AOSIP
DU
Click to expand...
Click to collapse
Could you please list the links for each ROM?

marcospheitosa said:
Could you please list the links for each ROM?
Click to expand...
Click to collapse
Most are already out of date fora long time.... and I am sure XDA Search works. last I tried...

KrisM22 said:
I have heard it both ways - bricked on MM or bricked on return to N. It's your phone. Just realize the chance you are taking.
I have found @AmulyaX 's
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
(7.1.2) to be fantastic on battery life. Much better than MM. It's what I use most of the time these days until Oreo gets sussed.
Click to expand...
Click to collapse
Thank you for this. I've just unlocked my bootloader and will flash it. Wheres the stable TWRP that could backup EFS perhaps? Could you provide link for rooting?

jeprox said:
Thank you for this. I've just unlocked my bootloader and will flash it. Wheres the stable TWRP that could backup EFS perhaps? Could you provide link for rooting?
Click to expand...
Click to collapse
Sorry for big delay - life keeps getting in the way...
TWRP that backs up EFS here:
https://forum.xda-developers.com/mo...overy-unofficial-twrp-3-2-1-0-option-t3743116
I had somebody's 3.2.1-0 and after second attempt was able to get it to flash it (choose "image")
Remember, with these TWRPs when you boot to it, the screen seems locked at menu so just tap pwr button and tap again and slide to unlock and you're good to go.
Scroll down Backup screen to see box for EFS.
There's also an app that backs up EFS (root I think).
For root I believe all I did was flash majisk 1530 zip in TWRP. -
To do that: flash ROM, flash gapps, install, then reboot to TWRP and flash 1530.
https://forum.xda-developers.com/apps/magisk
second post.
Oh I see 1531 is out, so try that.
1530 or 1531 will auto install magisk mgr so you don't have to do anything. root plus safetynet. Works fine for me. I'll be back in a bit.

Jimi Mack said:
Most are already out of date fora long time.... and I am sure XDA Search works. last I tried...
Click to expand...
Click to collapse
good night, I'm using several ROMs and testing on my zplay bike, the problems I'm encountering I've flagged. if I answered with the problems is because I liked the ROM, because the other ROMs that I did not like, nor signaled any mistakes. today I am in the last version of 8.1 AOSP, tomorrow I will quote bugs.

KrisM22 said:
Sorry for big delay - life keeps getting in the way...
TWRP that backs up EFS here:
https://forum.xda-developers.com/mo...overy-unofficial-twrp-3-2-1-0-option-t3743116
I had somebody's 3.2.1-0 and after second attempt was able to get it to flash it (choose "image")
Remember, with these TWRPs when you boot to it, the screen seems locked at menu so just tap pwr button and tap again and slide to unlock and you're good to go.
Scroll down Backup screen to see box for EFS.
There's also an app that backs up EFS (root I think).
For root I believe all I did was flash majisk 1530 zip in TWRP. -
To do that: flash ROM, flash gapps, install, then reboot to TWRP and flash 1530.
https://forum.xda-developers.com/apps/magisk
second post.
Oh I see 1531 is out, so try that.
1530 or 1531 will auto install magisk mgr so you don't have to do anything. root plus safetynet. Works fine for me. I'll be back in a bit.
Click to expand...
Click to collapse
successfully installed TWRP

jeprox said:
installing TWRP on the said link doesn't have instructions. Sorry but i'm just being careful.
Click to expand...
Click to collapse
This should help. don't forget to use the patcher in the code at the top if you haven't already or you won't be able to restore stock backups.
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629

Is there a Custom ROM for Huawei 7X/Mate SE?

Would like to use a clean version of Android instead of the EMUI version that is loaded on all their phones.
Seeing how these phones are identical, figured what would work for one would work with the other.
Thanks for giving me any insight.
Coming from the Galaxy Note 4 - hoping I'm not making a mistake with this phone that is enroute.

+1

Nothing happening on this phone I guess.

Jimi Mack said:
Nothing happening on this phone I guess.
Click to expand...
Click to collapse
Guess you haven't bothered looking at the ROMs and development section. While alot of ROMs are not what I would deem "daily material", their is working going on to get ROMs on this device.
Sent from my BND-L24 using Tapatalk

Here is a list of supported custom ROMs on Mate SE, Choose the A only ROM.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
The whole custom ROM world has changed, Now you need to apply system.img instead of rom.zip using fastboot command.
I have the PHH-Treble installed on my Huawei Mate SE. here is the link.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659

In addition, I'd check out the Open Kirin site. I've read the Lineage version is outstanding and well tuned for the chip. They list the 7x as supported but I've read the Mate SE most certainly is also.
https://openkirin.net/download/

nook'r said:
Here is a list of supported custom ROMs on Mate SE, Choose the A only ROM.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
The whole custom ROM world has changed, Now you need to apply system.img instead of rom.zip using fastboot command.
I have the PHH-Treble installed on my Huawei Mate SE. here is the link.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Click to expand...
Click to collapse
Learning about this phone, why the A only roms?

AsItLies said:
In addition, I'd check out the Open Kirin site. I've read the Lineage version is outstanding and well tuned for the chip. They list the 7x as supported but I've read the Mate SE most certainly is also.
https://openkirin.net/download/
Click to expand...
Click to collapse
I've been running the OpenKirin Lineage v4 on my Mate SE as daily driver for over a week. It is outstanding. Not going back to emui.

olswede said:
I've been running the OpenKirin Lineage v4 on my Mate SE as daily driver for over a week. It is outstanding. Not going back to emui.
Click to expand...
Click to collapse
Coincidentally, just booted that ROM (on my SE) today. It's very very good, noticed a few minor glitches to do with the camera and navigation (will let them know about em).
I'll admit though, emui8 is growing on me It's certainly better than 5.1 was. Love to see the roms becoming available though. No doubt when updates stop (or before), they will be critical to have.

AsItLies said:
Coincidentally, just booted that ROM (on my SE) today. It's very very good, noticed a few minor glitches to do with the camera and navigation (will let them know about em).
I'll admit though, emui8 is growing on me It's certainly better than 5.1 was. Love to see the roms becoming available though. No doubt when updates stop (or before), they will be critical to have.
Click to expand...
Click to collapse
I don't mind emui except that the power-saver regularly kills tasker, ad-blocking vpns, etc. I've tried everything to exempt them from power saving but no go. The battery life is outstanding though (I usually only lose 15% after a full day's usage), so for average users it's a bonus.

nook'r said:
Here is a list of supported custom ROMs on Mate SE, Choose the A only ROM.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
The whole custom ROM world has changed, Now you need to apply system.img instead of rom.zip using fastboot command.
I have the PHH-Treble installed on my Huawei Mate SE. here is the link.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Click to expand...
Click to collapse
Hey thanks for pointing me in the right direction. I have not installed a custom ROM in a long time.
---------- Post added at 08:44 AM ---------- Previous post was at 08:40 AM ----------
olswede said:
I've been running the OpenKirin Lineage v4 on my Mate SE as daily driver for over a week. It is outstanding. Not going back to emui.
Click to expand...
Click to collapse
This looks sweet, but the instruction on this site say I need my custom bootloader,and i can't find a guide how to do that. i have TWRP

AsItLies said:
Coincidentally, just booted that ROM (on my SE) today. It's very very good, noticed a few minor glitches to do with the camera and navigation (will let them know about em).
I'll admit though, emui8 is growing on me It's certainly better than 5.1 was. Love to see the roms becoming available though. No doubt when updates stop (or before), they will be critical to have.
Click to expand...
Click to collapse
Any chance you'd elaborate on the issues you've come across? I'm thinking about loading it up but don't want to lose functionality

JakeBuck said:
Any chance you'd elaborate on the issues you've come across? I'm thinking about loading it up but don't want to lose functionality
Click to expand...
Click to collapse
Nothing terribly serious. I didn't use it for long, but the camera option for selfie shutter 'palm to camera' didn't work. Also the recently taken shots didn't show in the bottom gallery (I read this is fixed now). And the navigation arrows at the bottom seemed to not be persistent somehow (after a reboot this was okay).
It's easy to go back to stock, except if you haven't backed everything up, have to reconfigure, add / subtract apps etc.
I'd suggest searching for the openKirin website, they seem to be doing the most development. Also follow their directions, they worked for me and pretty easy.

Hi
How does one flash the "Openkirin_los_beta4" Iso to the Mate SE (BND-L34)? TWRP?? Fastboot??? what are the exact steps to not render it a paper weight again lol; Do you need Magisk-v16.0 to root it as well?

Scythe69 said:
Hi
How does one flash the "Openkirin_los_beta4" Iso to the Mate SE (BND-L34)? TWRP?? Fastboot??? what are the exact steps to not render it a paper weight again lol; Do you need Magisk-v16.0 to root it as well?
Click to expand...
Click to collapse
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/

zackzuse said:
This looks sweet, but the instruction on this site say I need my custom bootloader,and i can't find a guide how to do that. i have TWRP
Click to expand...
Click to collapse
No, you don't need a custom bootloader.
You only need unlocked bootloader and unlocked frp.
TWRP is not supported on OpenKirin ROMs (especially on 7x twrp won't work).
You just need to flash the .img file through bootloader and then reboot to recovery and do a factory data reset.

Can anyone give me some advice: I have the Mate SE, currently on EMUI 8.0.0.332 (security update available but not installed), with TWRP and Magisk. I would love to install a custom ROM, but the OpenKirin site says TWRP isn't supported. Can I still install one of those builds and just expect no support if something goes wrong, or should I find some way to return to full stock before flashing? And if I need stock recovery, where can I find a download for it? I haven't had any luck on searching here yet.

Install Android 9.0 Pie on Honor 7X – AOSP 9.0 Pie ROM

youssef alonso said:
Install Android 9.0 Pie on Honor 7X – AOSP 9.0 Pie ROM
Click to expand...
Click to collapse
Has anyone tried this custom ROM? I would love to hear some success stories before possibly bricking my device

awlonsky said:
Has anyone tried this custom ROM? I would love to hear some success stories before possibly bricking my device
Click to expand...
Click to collapse
Pretty much any GSI works so long as you have updated to EMUI 8 sometime in the past.

Non-original screen stopped working after Oreo update

Hey there, I have this problem. I see others had it as well but I could not find any clear/reliable instructions in those threads. Currently I can interact with my phone only through an USB mouse.
Because I'd like to remain on the official update channel, is there any way to do it?
Otherwise, if I have to flash another ROM, where can I find a reliable (original?) Nougat image, and how do I prevent bricking? (I flashed other ROMs in the past and have some knowledge of the process, but it was always cyanogenmod/lineageos. This time I think I might brick something with the downgrade).
Thank you very much in advance!

MarkHopper said:
Hey there, I have this problem. I see others had it as well but I could not find any clear/reliable instructions in those threads. Currently I can interact with my phone only through an USB mouse.
Because I'd like to remain on the official update channel, is there any way to do it?
Otherwise, if I have to flash another ROM, where can I find a reliable (original?) Nougat image, and how do I prevent bricking? (I flashed other ROMs in the past and have some knowledge of the process, but it was always cyanogenmod/lineageos. This time I think I might brick something with the downgrade).
Thank you very much in advance!
Click to expand...
Click to collapse
I'm working on ParallelScreens Kernel for Oreo ARM and ARM64, wait a few days (OTA might not work afterwards though) and then flash it through TWRP.
Sent from my Moto G5S using XDA Labs

JarlPenguin said:
I'm working on ParallelScreens Kernel for Oreo ARM and ARM64, wait a few days (OTA might not work afterwards though) and then flash it through TWRP.
Click to expand...
Click to collapse
Wonderful! Meanwhile thanks to Gabriel @montanalabtesters I installed a 9.0–based ROM with ParallelScreens Depending on how it performs I might roll back to stock 8.1 with your kernel once it's out

MarkHopper said:
Wonderful! Meanwhile thanks to Gabriel @montanalabtesters I installed a 9.0–based ROM with ParallelScreens Depending on how it performs I might roll back to stock 8.1 with your kernel once it's out
Click to expand...
Click to collapse
Yep, I'm working on it. Maybe I'll do it the day after tomorrow, I'm not sure yet.
Sent from my Moto G5S using XDA Labs

Any updates on this @JarlPenguin? I also have the same problem, tried downgrading to Nougat, a few custom roms, but still, the screen stops working after a while.

fbmiranda7 said:
Any updates on this @JarlPenguin? I also have the same problem, tried downgrading to Nougat, a few custom roms, but still, the screen stops working after a while.
Click to expand...
Click to collapse
It's fixed on all up to date Pie ROMs and LineageOS 15.1.