Develop Bugs

(Android Oreo)MK81.0-nx563j-EXPERIMENTAL

flsah nx563j_firmware_515
MK81.0-nx563j-201805210138-EXPERIMENTAL
Magisk-v16.4
https://download.mokeedev.com/?device=nx563j
https://drive.google.com/drive/folders/1T4onVKVtUa8kmeMGrMoHuVu8hKzD7z5G?usp=sharing

kenzo_cz said:
flsah nx563j_firmware_515
MK81.0-nx563j-201805210138-EXPERIMENTAL
Magisk-v16.4
https://download.mokeedev.com/?device=nx563j
https://drive.google.com/drive/folders/1T4onVKVtUa8kmeMGrMoHuVu8hKzD7z5G?usp=sharing
Click to expand...
Click to collapse
Great news!

Any informations about steps of installation?
And now we wait for first impressions.

camera launching very slow

kolibre said:
camera launching very slow
Click to expand...
Click to collapse
How did you install this rom? And what rom had you before?

surfer30 said:
How did you install this rom? And what rom had you before?
Click to expand...
Click to collapse
you have to unlock bootloader and install twrp recovery before install 3rd party rom, go Google for tutorial. btw, this rom is not suitable for new flasher.

kolibre said:
you have to unlock bootloader and install twrp recovery before install 3rd party rom, go Google for tutorial. btw, this rom is not suitable for new flasher.
Click to expand...
Click to collapse
You flashed rom directly from trwp on existing rom?
I have unlocked phone and trwp recovery before I used different roms so far. Now I'm on RR, latest build by arceoxis

surfer30 said:
You flashed rom directly from trwp on existing rom?
I have unlocked phone and trwp recovery before I used different roms so far. Now I'm on RR, latest build by arceoxis
Click to expand...
Click to collapse
cool, then you can format data, clear system/data/cache/internal storage, after that install base band (the one with 5.15) then install rom, then install open gapps if you want, reboot, enjoy

Returns on this Rom? Bluetooth? GPS? Android Oreo? NFC?

Any widevine support? I can't go through the pain of installing yet another ROM unless it's perfect

Deeoon said:
Returns on this Rom? Bluetooth? GPS? Android Oreo? NFC?
Click to expand...
Click to collapse
ishurmer said:
Any widevine support? I can't go through the pain of installing yet another ROM unless it's perfect
Click to expand...
Click to collapse
same requirements here ^_^

MrBlubke said:
same requirements here ^_^
Click to expand...
Click to collapse
Anyone can try the ROM ?

I haven't tested IR blaster so far, but the only big that I found so far is the camera launching, it's so slow, the strange thing is that in the previous UNOFFICIAL build it was launching well, I hope he will fix it in the next build.

arceoxis said:
I haven't tested IR blaster so far, but the only big that I found so far is the camera launching, it's so slow, the strange thing is that in the previous UNOFFICIAL build it was launching well, I hope he will fix it in the next build.
Click to expand...
Click to collapse
from what I remember from another ROM is that this slow camera launch seems to fix itself after a few reboots (Lineageos 15.1 seemed to suffer from this too)
so, is bluetooth audio working? and what about widevine drm? haven't found any z17 oreo rom that has widevine support yet...

MrBlubke said:
from what I remember from another ROM is that this slow camera launch seems to fix itself after a few reboots (Lineageos 15.1 seemed to suffer from this too)
so, is bluetooth audio working? and what about widevine drm? haven't found any z17 oreo rom that has widevine support yet...
Click to expand...
Click to collapse
not this one, I have rebooted for so many times but lagging still remain, did not act like 15.1.
Bluetooth is searchable and should be pairabled. never tried yet since I don't have a good headset.

MrBlubke said:
from what I remember from another ROM is that this slow camera launch seems to fix itself after a few reboots (Lineageos 15.1 seemed to suffer from this too)
so, is bluetooth audio working? and what about widevine drm? haven't found any z17 oreo rom that has widevine support yet...
Click to expand...
Click to collapse
BT working flawlessly, I passed DRM info app and this were the results:

arceoxis said:
BT working flawlessly, I passed DRM info app and this were the results:
Click to expand...
Click to collapse
Ok, so they're definitely improving, but just not there yet...
Wonder what needs to be done for widevine support like this... (Screenshot from lineageos 14.1)

MrBlubke said:
Ok, so they're definitely improving, but just not there yet...
Wonder what needs to be done for widevine support like this... (Screenshot from lineageos 14.1)
Click to expand...
Click to collapse
It seems that I solved it, I've just copied vendor/lib/mediadrm/libwvdrmengine.so from other Oreo ROM and now it looks like this. I've attached a little flashable .zip with the patch, I hope it could help.

kenzo_cz said:
flsah nx563j_firmware_515
MK81.0-nx563j-201805210138-EXPERIMENTAL
Magisk-v16.4
Click to expand...
Click to collapse
Ok, I tried installing everything in one go adding each zip after the other in twrp... apparently, this doesn't work... Device just turns off again after Nubia logo (yes I did the normal wipe)
I did select to prevent to overwrite TWRP
update: apparently you need to boot the device between installing Rom (and open Gapps) and installing Magisk... installing magisk 16.4 apparently needs to be done later... I'll report back when I'm done

arceoxis said:
It seems that I solved it, I've just copied vendor/lib/mediadrm/libwvdrmengine.so from other Oreo ROM and now it looks like this. I've attached a little flashable .zip with the patch, I hope it could help.
Click to expand...
Click to collapse
Thanks for that arceoxis. The patch looks really promising; I'm going to try this later.

[ROOT] [MAGISK] [Module] Hardware Origin Bypass for Xiaomi devices

Hi All -
Just wanted to make a thread here to link to the Magisk Module I created that bypasses the bootloop we get when we have CN hardware with the Global Rom. I think this will work for India and Russia hardware too. Enjoy.
https://forum.xda-developers.com/apps/magisk/module-xiaomi-global-rom-cn-hardware-t3899316

PWn3R said:
Hi All -
Just wanted to make a thread here to link to the Magisk Module I created that bypasses the bootloop we get when we have CN hardware with the Global Rom. I think this will work for India and Russia hardware too. Enjoy.
https://forum.xda-developers.com/apps/magisk/module-xiaomi-global-rom-cn-hardware-t3899316
Click to expand...
Click to collapse
Thanks for this! Have you tested this to make sure stock camera still works without any issue?

xterminater07 said:
Thanks for this! Have you tested this to make sure stock camera still works without any issue?
Click to expand...
Click to collapse
Mine never stopped working before, however, this works completely differently. This inserts a script into the boot process that happens before the device starts launching system services that changes the ro.boot.hwc and ro.boot.hwcountry to be "global". The other way I was doing it was to make the product props to a value that would make it skip the checks entirely. Unfortunately, changing that value removed the slider settings, broke the slider camera, and for some, stopped the stock camera from working. I have checked an all expected settings are in the menu, safetynet passes, the slider works, the stock camera works.

Great, all works, no problem with camera or slider settings.

PWn3R said:
Mine never stopped working before, however, this works completely differently. This inserts a script into the boot process that happens before the device starts launching system services that changes the ro.boot.hwc and ro.boot.hwcountry to be "global". The other way I was doing it was to make the product props to a value that would make it skip the checks entirely. Unfortunately, changing that value removed the slider settings, broke the slider camera, and for some, stopped the stock camera from working. I have checked an all expected settings are in the menu, safetynet passes, the slider works, the stock camera works.
Click to expand...
Click to collapse
Eggcellent!!! lol... so just flash with twrp and that's it?

Yes, flash Magisk, 18.0 and 18.1 don't work for me. Use 17.3 and then flash this and you should be golden.

i dont know who created this, but this was shared on a Mi Mix3 FB group from PH.
Magisk-v18.1_mix3专版

bluviper said:
i dont know who created this, but this was shared on a Mi Mix3 FB group from PH.
Magisk-v18.1_mix3专版
Click to expand...
Click to collapse
does this work on chinese device with chinese rom or xiaomi eu rom?

I have got it working on chinese device with xiaomi.eu rom.

xterminater07 said:
does this work on chinese device with chinese rom or xiaomi eu rom?
Click to expand...
Click to collapse
I can confirm that works, I already flashed
Inviato dal mio MIX 3 utilizzando Tapatalk

yes, its working on EU ROM coz im on Mi-Globe which is based on EU ROM.

bluviper said:
yes, its working on EU ROM coz im on Mi-Globe which is based on EU ROM.
Click to expand...
Click to collapse
Why would you use it on the EU/Mi-Globe?

Mackay53 said:
Why would you use it on the EU/Mi-Globe?
Click to expand...
Click to collapse
before, V18.0 wont work with mix3.
no matter how you install it. only 17.3 works
as of the moment, since the week before the Chinese New Year, there are no updates from mi-globe. until this weekend. so this is a good alternative to make v18 work with mix3.

bluviper said:
before, V18.0 wont work with mix3.
no matter how you install it. only 17.3 works
as of the moment, since the week before the Chinese New Year, there are no updates from mi-globe. until this weekend. so this is a good alternative to make v18 work with mix3.
Click to expand...
Click to collapse
What benefits do v18 make over v17.3?

Mackay53 said:
What benefits do v18 make over v17.3?
Click to expand...
Click to collapse
Other than a new magisk manager interface I don't notice any difference.

954wrecker said:
Other than a new magisk manager interface I don't notice any difference.
Click to expand...
Click to collapse
That's what I was thinking but people seem to really want to install it, I'm still on 17.1 as that's what comes with twrp.

I haven't tested 18.1 as posted above, but 17.3 is the latest working released version for global.

PWn3R said:
I haven't tested 18.1 as posted above, but 17.3 is the latest working released version for global.
Click to expand...
Click to collapse
Most people on telegram are now using 18.1 , apparently support for modules will end soon for 17.

The released 18.0 and 18.1 do not work on the mix 3. I have no idea if the one linked above does, but I also don't know what they modified which is why I was advising 17.3
Sent from my Mi MIX 3 using Tapatalk

PWn3R said:
The released 18.0 and 18.1 do not work on the mix 3. I have no idea if the one linked above does, but I also don't know what they modified which is why I was advising 17.3
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
its working. some of the others guys here installed it.
they said its working. i for one, installed, and its working.
based on the screen capture i posted. you can see a logo of xda, maybe they are a part of it somehow.
moreover, there are tons of bulleted changelogs for the 18.0 & 18.1
some of them may not be noticeable for a very large audience, but this "i guess" will make it future proof for the reason of rom updates and compatibility. since Android Q is in the works.
also, noticed these changes
Code:
v18.1
- [General] Support EMUI 9.0
- [General] Support Kirin 960 devices
- [General] Support down to Android 4.2
- [General] Major code base modernization under-the-hood
other changes are for MagiskHide, maybe to better hide other apps. because there are some few apps that still can detect rooted devices even if they are HIDDEN.

[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.

Question Going back to original (MIUI Global stable) after flashing many custom roms

Hello, guys! I have a question for you; I hope you could help me out with this, I've been looking over the web and couldn't find anything.
First some background.
Right after I bought my POCO F3, I unlocked the bootloader and flashed the xiaomi.eu rom, I stayed there for months, but then I wanted to try some AOSP ROMs, so I flashed crDroid, it wasn't what I was looking for, so I switched to Pixel Experience, I was pretty happy with it but some banking apps didn't work even with Magisk and zygisk and all that stuff, so I tried to flash Pixel OS but their recovery didn't work for me, my last shot was Lineage OS, but it was similar to crDroid, long story short, I decided to go back to MIUI global.
I used the official MiFlash tool and flashed the latest release of MIUI global stable through fastboot.
My concern is the following, after flashing the original rom through fastboot with the option "clean_all" is the phone stays the same as before flashing all that stuff? If not, what should I do?
Somehow I feel like there is a huge mess in the internal memory and I just want to make sure that everything is formatted, cleaned and original, like it never had any custom rom installed before.

If you chose clean all it will be like Brandon new, take note if you leave the bootloader un locked it will not pass google play store of certification, how lame right ,they want you to lock the bootloader, that's why I chose Arrow

jefffrom said:
If you chose clean all it will be like Brandon new, take note if you leave the bootloader un locked it will not pass google play store of certification, how lame right ,they want you to lock the bootloader, that's why I chose Arrow
Click to expand...
Click to collapse
I didn't now that, I just installed safetynet test and it fails the CTS profile match
Can I just lock the bootloader again to go back to normal? I don't plan to keep messing around with custom roms again

woix said:
I didn't now that, I just installed safetynet test and it fails the CTS profile match
Can I just lock the bootloader again to go back to normal? I don't plan to keep messing around with custom roms again
Click to expand...
Click to collapse
Yes

jefffrom said:
Yes
Click to expand...
Click to collapse
Thanks bro, I'll do that

You don't need to lock the BL.
Get Magisk, enable Zygisk, and use the Magisk Module "SafetyNet Fix" from GitHub. The Module did the job for me.
Might also work on Pixel Experience. ^^
I'm currently just using Stock MIUI 13.

cyanGalaxy said:
You don't need to lock the BL.
Get Magisk, enable Zygisk, and use the Magisk Module "SafetyNet Fix" from GitHub. The Module did the job for me.
Might also work on Pixel Experience. ^^
I'm currently just using Stock MIUI 13.
Click to expand...
Click to collapse
I already did that in pixel experience, but there was just one banking app that didn't want to work no matter what I try. I really wanted to stay in pixel experience but now that I'm back in MIUI 13 with poco launcher 4 it's not that bad either, at least I have Dolby Atmos, HDR and all that stuff.

woix said:
I already did that in pixel experience, but there was just one banking app that didn't want to work no matter what I try. I really wanted to stay in pixel experience but now that I'm back in MIUI 13 with poco launcher 4 it's not that bad either, at least I have Dolby Atmos, HDR and all that stuff.
Click to expand...
Click to collapse
Yeah because of Dolby Atmos and MIUI Camera I'm also staying on MIUI. ^^
BTW, just to really make sure, you used Magisk Module "SafetyNet Fix" on Pixel Experience, yes?
You can try deleting the folder "TWRP" if existent (some apps check for that folder, e.g. Mario Kart). You can also try hiding Magisk App (apps also check for that app).

cyanGalaxy said:
Yeah because of Dolby Atmos and MIUI Camera I'm also staying on MIUI. ^^
BTW, just to really make sure, you used Magisk Module "SafetyNet Fix" on Pixel Experience, yes?
You can try deleting the folder "TWRP" if existent (some apps check for that folder, e.g. Mario Kart). You can also try hiding Magisk App (apps also check for that app).
Click to expand...
Click to collapse
Yes, All of that. I followed this tutorial btw

cyanGalaxy said:
Yeah because of Dolby Atmos and MIUI Camera I'm also staying on MIUI. ^^
BTW, just to really make sure, you used Magisk Module "SafetyNet Fix" on Pixel Experience, yes?
You can try deleting the folder "TWRP" if existent (some apps check for that folder, e.g. Mario Kart). You can also try hiding Magisk App (apps also check for that app).
Click to expand...
Click to collapse
if you want the goodies of MIUI but also to pass safetynet without issues i suggest you to try "xiaomi eu"
they are based on the chinese rom which is ahead in terms of features and bugfixes (specially the beta) and have some optimizations to make the experience better

emmanuelin14 said:
if you want the goodies of MIUI but also to pass safetynet without issues i suggest you to try "xiaomi eu"
they are based on the chinese rom which is ahead in terms of features and bugfixes (specially the beta) and have some optimizations to make the experience better
Click to expand...
Click to collapse
Tried it.. it's oky... I like Google System Apps more. Call Recording Feature was nice. :v
But unfortunately, GSI's didn't work/boot with Xiaomi.eu (Generic System Images). I like to be able to use GSI's, to try out other new OSes from time to time, Dual Boot sorta. ^^

Question Rollback to OOS13, need help please

Hey guys, sadly I have to come back to OOS as there is no human way to get bank apps running - when I unroot phone it works so somehow the apps are detecting magisk even with all the tweaks applied...
Actually I'm on android 13 with cr-droid custom rom, so which is the way to rollback to original rom?
thanks in advance

Yes there is many ways. Look bank apps source in java and see if it scan for root and patch it.

spamerobaldomero said:
Hey guys, sadly I have to come back to OOS as there is no human way to get bank apps running - when I unroot phone it works so somehow the apps are detecting magisk even with all the tweaks applied...
Actually I'm on android 13 with cr-droid custom rom, so which is the way to rollback to original rom?
thanks in advance
Click to expand...
Click to collapse
Flash oos over fastbootd
(With fbe)

JonasHS said:
Yes there is many ways. Look bank apps source in java and see if it scan for root and patch it.
Click to expand...
Click to collapse
Hmmm that sounds too difficult for my knowledge

ChrisFeiveel84 said:
Flash oos over fastbootd
(With fbe)
Click to expand...
Click to collapse
what's fbe? I thought the way would be MSM