Database Develop

[MODULE][SYSTEM/LESS] ART Optimization v2.0 [DISCONTINUED]

Android Runtime Optimization
DISCONTINUED lol
Android Lollipop includes a new virtual machine called ART (Android Runtime.) ART uses AOT (ahead-of-time) compilation into native code, which performs better than JIT (just-in-time) compilation into bytecode. You can configure ART to perform this optimization in different ways. Android Lollipop includes the dex2oat tool for optimizing applications on deployment.
Click to expand...
Click to collapse
Compiler Filters
Since Lollipop, dex2oat takes a variety of --compiler-filter options to control how it compiles. Passing in a compiler filter flag for a particular app specifies how it’s pre-optimized. Here’s a description of each available option:
everything - compiles almost everything, excluding class initializers and some rare methods that are too large to be represented by the compiler’s internal representation.
speed - compiles most methods and maximizes runtime performance, which is the default option. ** default value on this module
balanced - attempts to get the best performance return on compilation investment.
space - compiles a limited number of methods, prioritizing storage space.
interpret-only - skips all compilation and relies on the interpreter to run code.
verify-none - special option that skips verification and compilation, should be used only for trusted system code.
This module sets a few dalvik.vm and pm.dexopt properties:
Code:
dalvik.vm.dex2oat-filter [B]**editable with the given compiler filters[/B]
dalvik.vm.image-dex2oat-filter
pm.dexopt.bg-dexopt
dalvik.vm.check-dex-sum
dalvik.vm.checkjni
dalvik.vm.usejit
dalvik.vm.heaptargetutilization
dalvik.vm.dex2oat-threads
Magisk Module (UI in Terminal Emulator)
How to use:
Open Terminal Emulator
Type su and then
Code:
art_magisk
Then choose your filter
Non-Magisk (command line)
How to use:
Code:
ART Optimization by veez21
setfilter [--compiler-filter] [file]
compiler filters:
everything
speed
balanced
space
interpret-only
verify-none
Ex:
Code:
setfilter everything
** this will find the file on common/default directories
Code:
setfilter everything /system/su.d/name.sh
** this will use the directory you entered, instead of the defaults
MORE INFORMATION ON THIS TOPIC HERE and here
UNIFIED INSTALLER IS PRESENT SINCE v1. IT INSTALLS IN A SPECIFIED ORDER (look below) . SO IF YOU DON'T HAVE MAGISK, YOU CAN STILL FLASH THE ZIP IN THE DOWNLOADS!
Order of Detection during Installation:
Code:
> Magisk > Systemless SuperSU > System SuperSU > Init.d
AFTER FLASHING, FOR THE FIRST TIME, WIPE DALVIK/ART CACHE. THIS IS NEEDED FOR IT TO TAKE EFFECT. YOU DON'T HAVE TO WHEN UPDATING THOUGH
THAT'S WHY YOU HAVE TO CHANGE THE --compiler-filter IF YOU WANT MORE APP PERFORMANCE. speed BEING THE DEFAULT IN ROMS (IF THE DEV HAVEN'T CHANGED IT), YOU CAN CHANGE IT TO everything IF YOU WANT MORE PERFORMANCE (BUT COSTS MORE SPACE). IDEAL VALUE WOULD BE balanced IF YOU ASK ME.
** This module can have problems with heavily modified OEM Roms (e.g. TouchWiz, MIUI). YOU HAVE BEEN WARNED. But this problem is inconsistent and just might work for you.
Read this Samsung ROM users: https://forum.xda-developers.com/showpost.php?p=72401085&postcount=594 ** possibly fixed on v1.3+
MOD Edit Links Removed Download here[/URL] or at Magisk Manager ** install in recovery
README and Changelogs
Uninstaller
Crash Fix
Source
Source (Magisk Repo)
MOD Edit Links Removed
DONATE? If you want to (ﾉ･ω･)ﾉﾞ

F.A.Q.
How to see if the changes are applied?
See Magisk log. ART Optimizations should be able to log there
Do this command and search for the properties given at the first post and if it there, it's working
Code:
su
getprop | grep dalvik
Bootloop! Help me!
Uninstall the module! Uninstaller
When in Magisk, RIL doesn't work, some apps crash, HELP!
Try flashing the crash fix. It might/might not work
Xposed not responding properly! Help me!
Can't do anything about it. Try wiping dalvik-cache, if that doesn't work uninstall the module
I don't use Magisk. How to can I use this?
Flash the zip at the OP. It installs to System if Magisk is not detected
I had some kind of trouble when using everything filter. Solution?
Try changing to speed. Several users have some trouble with everything too.
SuperSU + Magisk + This module is causing bootloop/some kind of problem. What do I do?
Uninstall the Magisk Module and install Non-Magisk instead

So by default this module should increase the speed of apps?
Enviado desde mi Aquaris X5 Plus mediante Tapatalk

Gonfebo said:
So by default this module should increase the speed of apps?
Enviado desde mi Aquaris X5 Plus mediante Tapatalk
Click to expand...
Click to collapse
Theoratically, yes, at first boot. After flashing wipe Dalvik/ART cache and see. :good:

Any Uninstaller to uninstall it ?
Does it work with Magisk ?
Sent from my YU5010 using Tapatalk

amihir said:
Any Uninstaller to uninstall it ?
Does it work with Magisk ?
Click to expand...
Click to collapse
Works with magisk since it's a magisk module ?. You can uninstall it in Magisk Manager

UPDATE TO v0.2!
Changelog:
- post-fs-data.sh and service.sh is additionally used to set properties
- fixed setting dalvik.vm.image-dex2oat-filter
Download

This module isn't needed on Nougat am I correct?

An XDA User said:
This module isn't needed on Nougat am I correct?
Click to expand...
Click to collapse
It can be used in nougat. I don't know the result of using it in it but try testing it and tell me the results if there's any problem

veez21 said:
It can be used in nougat. I don't know the result of using it in it but try testing it and tell me the results if there's any problem
Click to expand...
Click to collapse
Working fine on Nougat here.
I have a feeling that Plex (my media player) is MUCH snappier. And no, it hans't been updated lately.
Everything working... but I can't point a finger at anything else besides Plex.
Cheers!

If just edit system.prop with
dalvik.vm.dex2oat-filter=interpret-only
dalvik.vm.image-dex2oat-filter=speed
it should be work?

Hello m8 o/
Can you provide more download links?
"SYSTEM NOTICE: We apologize for any issues loading the site. We are working on a solution right now. Thanks for the understanding."
"Invalid response from the server: 502"
So when i can download this file i 1. Flash it in Magisk? 2. Flash it in TWRP?

Tesla said:
Hello m8 o/
Can you provide more download links?
"SYSTEM NOTICE: We apologize for any issues loading the site. We are working on a solution right now. Thanks for the understanding."
"Invalid response from the server: 502"
So when i can download this file i 1. Flash it in Magisk? 2. Flash it in TWRP?
Click to expand...
Click to collapse
2.Flash in TWRP
According to the OP, the mod requires wiping delvik/cashe after flashing the mod to work.

JERW28 said:
2.Flash in TWRP
According to the OP, the mod requires wiping delvik/cashe after flashing the mod to work.
Click to expand...
Click to collapse
:good:
Download works at the moment.
Edit: My phone (Note 4) is really fast as it is, but initial testing shows a bit faster launch of camera app.
Sure, it might be placebo. Hard to know just yet

Umm...
No... You've got this backwards...
Apps would launch slower... Not quicker... As your first boot is quicker... At least with the flags mentioned at the top of the post...
If you're looking for what would be faster app launch... You'd want to use the 'everything' flag as it builds a much larger cache file...
Sent from my Nexus 6 using Tapatalk

Tesla said:
Hello m8 o/
So when i can download this file i 1. Flash it in Magisk? 2. Flash it in TWRP?
Click to expand...
Click to collapse
I just installed it normally as a Magisk module. And wiped cache and dalvik on first reboot.

alroger said:
I just installed it normally as a Magisk module. And wiped cache and dalvik on first reboot.
Click to expand...
Click to collapse
That was my thought also, but it so simple to ge straight to TWRP so.

Thanks for the development and module for Magisk.
The effect is contrary with a Note 7 (MM) ported for SM N9005.
Installation according to indications, the smartphone is slower when starting up another 20 seconds.
There is no problem or fc but identically android lag enormously.
Perhaps a problem with the management of the kernel, ram ... etc
I tried to modify the filters without success for me.
A little feedback.
Thank you

This module sounds very interesting, but i have one question that isnt so clear to me... Does it speed up the start of apps in general or is it just the first start of the system after wiping dalvik/cache?

Just the first start thus it's pretty useless IMO. Mind you, it'll make apps perform worse.

[DEPRECATED] [2019.4.4] Magisk Manager for Recovery Mode (mm)

THIS PROJECT IS NO LONGER SUPPORTED.
# Magisk Manager for Recovery Mode (mm)
## LEGAL
Copyright (C) 2017-2019, VR25 @ xda-developers
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
## DISCLAIMER
Always read/reread this reference prior to installing/upgrading this software.
While no cats have been harmed, the author assumes no responsibility for anything that might break due to the use/misuse of it.
To prevent fraud, do NOT mirror any link associated with this project; do NOT share builds (zips)! Share official links instead.
## DESCRIPTION
- Manage your Magisk modules from recovery (e.g., TWRP) -- run "sh /sdcard/mm" on recovery terminal.
Features list
- Automatically fix magisk.img (e2fsck -fy)
- List installed modules
- Toggle
- Core only mode
- Magic mount
- Disable
- Remove
## PREREQUISITE
- Magisk 17-19
## SETUP
- Install
1. Flash live (e.g., from Magisk Manager) or from custom recovery (e.g., TWRP).
- Uninstall
- Use Magisk Manager app or mm itself (supports `uninstall.sh`, too).
## USAGE
- First time (right after installing/updating) - run `mm` or `sh /sdcard/mm` on recovery terminal.
- Next times (while in recovery) - no need to re-flash the zip; simply run `sh /sdcard/mm` on recovery terminal.
- Follow the instructions/wizard. Everything is interactive.
- Pro tip: lazy people can try running `*/mm` instead of `sh /sdcard/mm`.
## LINKS
- [Donate](https://paypal.me/vr25xda/)
- [Facebook page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git repository](https://github.com/Magisk-Modules-Repo/mm)
- [Telegram channel](https://t.me/vr25_xda/)
- [Telegram profile](https://t.me/vr25xda/)
- [XDA thread](https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165)
## LATEST CHANGES
**2019.4.4 (201904040)**
- Complete redesign
- Magisk 17-19 support (including `uninstall.sh`)
- Toggle core only mode
- Updated information (copyright, documentation, and module description)
**2018.8.1 (201808010)**
- General optimizations
- New & simplified installer
- Striped down (removed unnecessary code & files)
- Updated documentation
**2018.7.24 (201807240)**
- Fixed modPath detection issue (Magisk 16.6).
- Updated documentation

Archive

Hey not sure whether this is right thread to ask, if not please redirect me.
I'm on AOKP, banking apps are detecting root and not allowing to access it, so I was asked to use Magisk.
Can you tell me how do I install it? Can I just download Magisk Manager and Magisk flash it via twrp? I'm noob to all rooting man

BackToAndroid said:
Hey not sure whether this is right thread to ask, if not please redirect me.
I'm on AOKP, banking apps are detecting root and not allowing to access it, so I was asked to use Magisk.
Can you tell me how do I install it? Can I just download Magisk Manager and Magisk flash it via twrp? I'm noob to all rooting man
Click to expand...
Click to collapse
Yeah... You took a serious wrong turn.
Start by reading these threads:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
And if you need help, post here (with lots of details):
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

Sorry, maybe for my language, but I can not understand what this module is doing.
Enviado desde mi MI 5s Plus mediante Tapatalk

Hi,
Great idea! I'll check and comment. :good:
Please, add it to the official repository.
It includes one option to enable/disable Magisk Core Mode Only?
And one suggestion: provide a ZIP file for launch directly the "mm" command without opening the Terminal (or use Aroma Installer).

Nitram08 said:
Sorry, maybe for my language, but I can not understand what this module is doing.
Enviado desde mi MI 5s Plus mediante Tapatalk
Click to expand...
Click to collapse
You should at least have basic understanding of what Magisk is and how it operates before jumping onto this thread. If you don't know what I mean by "Magisk Manager for Recovery Mode," then you've been skipping steps. I can't help you before you help yourself.
manos78 said:
Hi,
Great idea! I'll check and comment. :good:
Please, add it to the official repository.
It includes one option to enable/disable Magisk Core Mode Only?
And one suggestion: provide a ZIP file for launch directly the "mm" command without opening the Terminal (or use Aroma Installer).
Click to expand...
Click to collapse
Currently limited to the features listed. New capabilities will be added over time. The ability to manage Magisk settings is already in the works. Repo submission status -- awaiting approval.

Firstly, thank you. I've used another mod that allows using terminal to get rid of modules but it's not as fluid in usage as this one. However, i have one question; While i was able to use it in recovery, I'm not sure I understand clearly about whether or not this can be used while the system is fully loaded. I tried accessing the app through the os terminal but it acts as if I'm entering the wrong command. In twrp i did as you said and typed "mm" and it pulled right up. Yet, when i try the instructions that follow afterward to access the module while in the os, it tells me it can't be found. Am i missing something or is this only available through recovery?

dodgyme said:
Firstly, thank you. I've used another mod that allows using terminal to get rid of modules but it's not as fluid in usage as this one. However, i have one question; While i was able to use it in recovery, I'm not sure I understand clearly about whether or not this can be used while the system is fully loaded. I tried accessing the app through the os terminal but it acts as if I'm entering the wrong command. In twrp i did as you said and typed "mm" and it pulled right up. Yet, when i try the instructions that follow afterward to access the module while in the os, it tells me it can't be found. Am i missing something or is this only available through recovery?
Click to expand...
Click to collapse
The "module" part is only meant for updating the tool through Magisk Manager.
So, you don't have to constantly check XDA/GitHub for newer versions.
@Nitram08, if that's what you meant, sorry about the first answer! Next time, PLEASE give more detail, or you might get very similar reactions.
A basic rule of thumb:
- Poor info = "nothing happened -- bad post".

Hmmmmm
So, just to clarify, it can only be used in twrp? If not, what's the exact command to use when I'm actually in the Android system using whatever terminal app I might be using...???
I ask because this part of your instructions confuses me:
"Else (after installing & rebooting) -- run `. /data/magisk/mm`."
My understanding suggests I can use it while in the actual system but when I use my terminal app it tells me it's not found...

dodgyme said:
So, just to clarify, it can only be used in twrp? If not, what's the exact command to use when I'm actually in the Android system using whatever terminal app I might be using...???
I ask because this part of your instructions confuses me:
"Else (after installing & rebooting) -- run `. /data/magisk/mm`."
My understanding suggests I can use it while in the actual system but when I use my terminal app it tells me it's not found...
Click to expand...
Click to collapse
Yeah... that line should be "after installing & rebooting into recovery". So, this is built for use in recovery mode only.
Instead of re-flashing every single time you need it, you simply run ". /data/magisk/mm" That is "dot space /magisk/mm".
In short
- First time (right after installing/updating) -- run "mm" (on recovery terminal)
- Next times (while in recovery) -- no need to re-flash the zip; simply run ". /data/magisk/mm" on terminal.

VR25 said:
Yeah... that line should be "after installing & rebooting into recovery". So, this is built for use in recovery mode only.
Instead of re-flashing every single time you need it, you simply run ". /data/magisk/mm" That is "dot space /magisk/mm".
In short
- First time (right after installing/updating) -- run "mm" (on recovery terminal)
- Next times (while in recovery) -- no need to re-flash the zip; simply run ". /magisk/mm" on terminal.
Click to expand...
Click to collapse
Understood, I appreciate your feedback and this little gem greatly. Thank you!

Type wrong, please ignore

I just want to thank Op for this. I can't tell you how many times I have gotten a bootloop from a faulty module making me have to delete magisk.img (always trying new things ). This makes it so much easier. Thanks much OP.

Thanks a bunch OP. This will be a life saver for those who don't take TWRP backups in TWRP before flashing a module, including me.
Sent from my Honor 8 Pro using XDA Labs

Magisk log: "e 432:569 sendfile failed with 2: No such file or directory"
Any Modules can not find after install this
New modules installs but not works and not shows on list of android magisk manager.
Very Poor soft! Need to repair system after that!
Unistall_magisk.zip not repair this error!
I lost my system???
Android AOSP (Aex) latest 7.1.2
Xiaomi redmi 4x

Amazing module, allows me to manage magisk in TWRP without issue. This is an essential module for every magisk user - if you can't boot after a module install, you can just remove the module and not worry about restoring a backup.
As an aside, also always have the Magisk uninstaller zip handy, it'll save your ass when your phone / tablet goes to **** when you're flashing modules like a meth addict.

Great module, but I found something weird on my phone...
Is there any reason why a removed/disabled moduled would appear as such in the current TWRP session or just after rebooting from TWRP to recovery, but reappear after powering off and then booting to recovery via bootloader?
This (strange) thing happened to me minutes ago and the only way to remove the module (and boot Android again) was uninstalling and then reinstalling Magisk...

Disable modules
I'm trying to disable a module but I don't entirely understand the commands. I start Magisk Manager and select "e" to enable/disable modules. Then it shows:
<Toggle Module ON/OFF>
Greenify4Magisk (ON)
aik-mobile (ON)
mm (ON)
Input a matching WORD/string at once
- Press RETURN when done (or to cancel)
-- CTRL+C to exit
What command do I have to use to disable Greenify4Magisk?

iqubik said:
Magisk log: "e 432:569 sendfile failed with 2: No such file or directory"
Any Modules can not find after install this
New modules installs but not works and not shows on list of android magisk manager.
Very Poor soft! Need to repair system after that!
Unistall_magisk.zip not repair this error!
I lost my system???
Android AOSP (Aex) latest 7.1.2
Xiaomi redmi 4x
Click to expand...
Click to collapse
Really good way of providing "useful" information...
You're dealing with different issues not related to this module in the first place. Could you describe exactly what you did and what actually happened afterwards?
njascgil said:
Great module, but I found something weird on my phone...
Is there any reason why a removed/disabled moduled would appear as such in the current TWRP session or just after rebooting from TWRP to recovery, but reappear after powering off and then booting to recovery via bootloader?
This (strange) thing happened to me minutes ago and the only way to remove the module (and boot Android again) was uninstalling and then reinstalling Magisk...
Click to expand...
Click to collapse
Odd...
Could you describe in details what you did to remove/disable the module in question?
beavis5706 said:
I'm trying to disable a module but I don't entirely understand the commands. I start Magisk Manager and select "e" to enable/disable modules. Then it shows:
<Toggle Module ON/OFF>
Greenify4Magisk (ON)
aik-mobile (ON)
mm (ON)
Input a matching WORD/string at once
- Press RETURN when done (or to cancel)
-- CTRL+C to exit
What command do I have to use to disable Greenify4Magisk?
Click to expand...
Click to collapse
You simply type a "matching WORD/string" and press ENTER. For example, to disable Greenify4Magisk, I would input "Green" or "4" or "Magisk" (whatever is unique to Greenify4Magisk).

TWRP install

Copying instructions that were in the miscellaneous thread while we were waiting for a proper sub forum. Keep in mind that the program to get TWRP onto the phone is in Chinese and will trigger an antivirus warning. Also TWRP will be in Chinese so users have to press the button on the right in the 1st screen to enable English.
TWRP is working for Nubia Z20 Chinease, Europe and American version
Download TWRP from this link
[Mod Edit] Download link removed due to GPL incompliance
Installing TWRP steps:
1. Enable usb debugging in nubia z20
2. Connect your mobile to the computer
3. Disable Anti-virus on your computer
4. Copy paste TWRP application to C:/adb
5. Click the only button on the TWRP interface
6. On the next screen, click the only button (fastboot twrp) on the screen
7. mobile will reboot to bootloader
8. reboot to recovery
9. if you have security code, input your security pin.
10. change language by clicking right side button
11. In twrp, you can flash global rom and magisk for root
For Rooting Nubia (all version)
1. Install TWRP from the above link
2. From TWRP, you can install magisk manager (latest) and reboot to system.
3. From Magisk application, download riru modules (core & hook) install and reboot.
4. Insatll Edxposed for xposed modules
Custom modules working for Nubia:
1. Gravity Box (working only for global roms)
2. Face unlock (Magisk module)
3. Instant Face unlock (Xposed module)
4. Pixelify (Magisk module0
5. Force touch enabler (Xposed module)
6. Xposed edge (Xposed module)
7. AR core patcher (Magisk module)
8. Google cam (Gcam shared earliet posts with attached xml scripts)
9. Youtube vanced
10. Whatsapp emojis
11. L Tweaks

Linux?
What should Linux users do?

Cheako said:
What should Linux users do?
Click to expand...
Click to collapse
Switch to windows? Seriously...at least for a short time. I'm a Linux user myself but always have a Windows machine handy for flashing

n1tro said:
Switch to windows? Seriously...at least for a short time. I'm a Linux user myself but always have a Windows machine handy for flashing
Click to expand...
Click to collapse
Thanks! I haven't used Windows since the late 90s and every time I try what you're suggesting I have a horrible time. It's not worth any amount of effort to have Windows for running this one application that does something ultimately resulting in Malware. That is to say running this program is analogous to running an application that, I not only don't have the source too, but indeed can't even explain what it does. That's the vary definition of malicious software, running software that has no explainable purpose.

It piss me off why every nubia TWRP is a .exe can you just install it yourself and make a backup of your recovery partition and send us the img ?
its here ***
[Mod Edit] Download link removed due to GPL incompliance

GPL Violation.
This program is obviously linked with a compiled image of TWRP, witch is GPL. The exe is encrypted, a form of UPX. Regardless it's against copyright to distribute without source.

RomanLeFrais said:
It piss me off why every nubia TWRP is a .exe can you just install it yourself and make a backup of your recovery partition and send us the img ?
its here ***
[Mod Edit] Download link removed due to GPL incompliance
Click to expand...
Click to collapse
Looks like a boot image, but triggers the same error on my device. From another thread we are discussing the differences of V1.x(NON-EU) and phones from the EU that are V2.x. The images I've found and have been using are V2.x and the phone is from US Amazon, not that you can't purchase EU phones from there. It's unknown what version my phone is.
I've been pointing out everywhere the GPL violations and that also applies here.

Tell me if I'm wrong but the only difference beteween eu and non-eu are the radio frequency and maybe some minor adjustement that don't affect the way TWRP work, and the only difference between 1.x and 2.x are the system update it also don't affect the way TWRP need to be compiled except for the included magisk install ect in the advanced tabs that Scarlet-glass added
If you want to have your own clean version you can always compile TWRP yourself to not deal with a GPL issue (Isn't it the GNU Free software license ?) Scarlet-glass released the device tree
UPX is a compression algorithm lol, to check if its obfuscated run Detect-it-Easy on it, I did and its not obfuscated take a look at my binwalk output
https://pastebin.com/7Ut6E5Zz
The executable maybe came from the person that make the "Global" ROM for all the aliexpress seller by removing the chinese app and installing google, they left their "weibo VIP channel" in /etc on the system part but I don't know how to join.
So anyway I doubt they copyrighted their TWRP image and its normal that the recovery image appear as a boot image because it is one lol

Apparently this device is not the same for EU users as America or China, that is to say one model for EU and another model for NON-EU(presumably China, India, Japan, Canada, US, ect). I was using V2.x(EU) files, but my phone is V1.x(NON-EU). The major version numbers are more like part of the model number than like a version indicator. Here is the full dump where I got the boot and recovery images, it's 2.2GB compressed
https://www.filehosting.org/file/details/835328/NX627J_NubiaEmergencyDownload_V103.7z
I'll try and post just the boot/recovery images here: https://mikemestnik.net/archives/
Code:
SHA256 (NX627J_NubiaEmergencyDownload_V103.7z) = bd412eeab191c001a4ee5b11bda8a2ec7273257ccd2e1d024e60e8c6a1bd174b
SHA256 (NX627J-stock-1_03.7z) = f53a120dc7e8029bf2bb0fb7a462d027376d63bb39e4b7f2ae2f55ae2bcba9ae

RomanLeFrais said:
Tell me if I'm wrong but the only difference beteween eu and non-eu are the radio frequency and maybe some minor adjustement that don't affect the way TWRP work, and the only difference between 1.x and 2.x are the system update it also don't affect the way TWRP need to be compiled except for the included magisk install ect in the advanced tabs that Scarlet-glass added
If you want to have your own clean version you can always compile TWRP yourself to not deal with a GPL issue (Isn't it the GNU Free software license ?) Scarlet-glass released the device tree
UPX is a compression algorithm lol, to check if its obfuscated run Detect-it-Easy on it, I did and its not obfuscated take a look at my binwalk output
https://pastebin.com/7Ut6E5Zz
The executable maybe came from the person that make the "Global" ROM for all the aliexpress seller by removing the chinese app and installing google, they left their "weibo VIP channel" in /etc on the system part but I don't know how to join.
So anyway I doubt they copyrighted their TWRP image and its normal that the recovery image appear as a boot image because it is one lol
Click to expand...
Click to collapse
The file you are talking about and the one that is currently posted are nothing alike.
Code:
[email protected]:~/Downloads$ binwalk nubia\ Z20-for\ Android\ P-TWRP-3.3.1.exe
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Microsoft executable, portable (PE)
372399 0x5AEAF SHA256 hash constants, little endian
4642204 0x46D59C MySQL ISAM compressed data file Version 10
13113062 0xC816E6 gzip compressed data, last modified: 2019-08-30 09:47:28
42228777 0x2845C29 End of Zip archive, footer length: -25518
42279022 0x285206E PARity archive data - file number 7950
42571120 0x2899570 XML document, version: "1.0"
This reminds me to add checksums to my uploads!

Cheako said:
The file you are talking about and the one that is currently posted are nothing alike.
This reminds me to add checksums to my uploads!
Click to expand...
Click to collapse
I first decompressed with upx
Code:
upx -d nubia\ Z20-for\ Android\ P-TWRP-3.3.1.exe
Edit: I downloaded 1.03 and 2.03 and try to look for diff in some files with
Code:
vimdiff <(xxd "EUROPE-ASIA/file" ) <(xxd "US/file" )
and they are a little different I didn't try the android files (system,vendor,boot etc) because they are too big though

RomanLeFrais said:
I first decompressed with upx
Code:
upx -d nubia\ Z20-for\ Android\ P-TWRP-3.3.1.exe
Edit: I downloaded 1.03 and 2.03 and try to look for diff in some files with
Code:
vimdiff <(xxd "EUROPE-ASIA/file" ) <(xxd "US/file" )
and they are a little different I didn't try the android files (system,vendor,boot etc) because they are too big though
Click to expand...
Click to collapse
help me please i am some speak english. my nubia z20 brick . i need stock rom my phone global en v203 i want to chinese rom but my phone brick.
i need rom i need help

Not working for me.....
Not able to install TWRP.
Have also tried to install img.
Have typed in "adb reboot bootloader" in command window, and the phone reboot.
But when typing "fastboot flash recovery recovery.img", it get stuck on "waiting for device".
Anyone have the correct USB driver?
Or is the problem windows 10?
Btw, USb debugging is on, and OEM unlocking is on.
Ui is CNCommon_V2.17.
The China special with no update function, beside update by usb-c OTG, wich don't work.

Why can not create backup from TWRP, both to the internal memory and to the flash card via OTG, writes an error.

Olfoss said:
Not able to install TWRP.
Have also tried to install img.
Have typed in "adb reboot bootloader" in command window, and the phone reboot.
But when typing "fastboot flash recovery recovery.img", it get stuck on "waiting for device".
Anyone have the correct USB driver?
Or is the problem windows 10?
Btw, USb debugging is on, and OEM unlocking is on.
Ui is CNCommon_V2.17.
The China special with no update function, beside update by usb-c OTG, wich don't work.
Click to expand...
Click to collapse
please answer me

n1tro said:
Copying instructions that were in the miscellaneous thread while we were waiting for a proper sub forum. Keep in mind that the program to get TWRP onto the phone is in Chinese and will trigger an antivirus warning. Also TWRP will be in Chinese so users have to press the button on the right in the 1st screen to enable English.
TWRP is working for Nubia Z20 Chinease, Europe and American version
Download TWRP from this link
https://drive.google.com/file/d/1rpyehWTPdzzNLhZVqvOuaPmoZ0bG0gak/view?usp=sharing
Installing TWRP steps:
1. Enable usb debugging in nubia z20
2. Connect your mobile to the computer
3. Disable Anti-virus on your computer
4. Copy paste TWRP application to C:/adb
5. Click the only button on the TWRP interface
6. On the next screen, click the only button (fastboot twrp) on the screen
7. mobile will reboot to bootloader
8. reboot to recovery
9. if you have security code, input your security pin.
10. change language by clicking right side button
11. In twrp, you can flash global rom and magisk for root
For Rooting Nubia (all version)
1. Install TWRP from the above link
2. From TWRP, you can install magisk manager (latest) and reboot to system.
3. From Magisk application, download riru modules (core & hook) install and reboot.
4. Insatll Edxposed for xposed modules
Custom modules working for Nubia:
1. Gravity Box (working only for global roms)
2. Face unlock (Magisk module)
3. Instant Face unlock (Xposed module)
4. Pixelify (Magisk module0
5. Force touch enabler (Xposed module)
6. Xposed edge (Xposed module)
7. AR core patcher (Magisk module)
8. Google cam (Gcam shared earliet posts with attached xml scripts)
9. Youtube vanced
10. Whatsapp emojis
11. L Tweaks
Click to expand...
Click to collapse
please can you improve twrp for android 11 this way

I can't. I'm not a developer. The information above was done by someone else before the forum was created. I only copied the content over.
This phone has almost no support unless you are using the Chinese version. Nubia does not care about the global market as they make enough money selling phones within China in my opinion.

n1tro said:
I can't. I'm not a developer. The information above was done by someone else before the forum was created. I only copied the content over.
This phone has almost no support unless you are using the Chinese version. Nubia does not care about the global market as they make enough money selling phones within China in my opinion.
Click to expand...
Click to collapse
i will never buy a nubia phone again.

I upgraded to android 11 beta for nubia z20, it installed without issue, but I was not satisfied with the upgrade because I could not access my contacts. I tried to reinstall the standard ROM back, it loads the nubia logo and then shows the warning “Device is corrupted. It can't be trusted and won't boot. " I have flashed the Nubia z20 unbrick tool v1.03 and this does not help either, please help

[MODULE] Debugging modules: ADB Root, SELinux Permissive, Enable Eng

These modules are not meant for everyday use. They are intended for debugging and modification of a firmware. They significantly lower security of your device while active and even could softbrick it. You've been warned.
ADB Root
Magisk Module that allows you to run "adb root". adb root is not an ordinary root (su), it's adbd daemon running on your phone with root rights. adb root allows you to "adb push/pull" to system directories and run such commands as "adb remount" or "adb disable-verify".
Download v1.0: https://github.com/evdenis/adb_root/releases/download/v1.0/adb_root.zip
Source code: https://github.com/evdenis/adb_root
Support: Telegram
SELinux Permissive
This module switches SELinux to permissive mode during boot process. This module intentionally lowers security settings of your phone. Please don't use it if there is a better solution to your problem, e.g., magiskpolicy. The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels.
Download v2.0: https://github.com/evdenis/selinux_permissive/releases/download/v2.0/selinux_permissive_v2.0.zip
Source code: https://github.com/evdenis/selinux_permissive
Support: Telegram
Enable Eng
This Magisk Module enables engineering build props. It allows to activate debugging parts of a firmware. Please, disable Magisk Hide for this module. If you don't know what you are doing, don't use this module. It can easily softbrick your device.
Troubleshooting
If your device doesn't boot then you need to reboot to TWRP recovery and
Code:
$ adb shell rm -fr /data/adb/modules/enable_eng
If ADB doesn't work that means adbd in your firmware is build without ALLOW_ADBD_ROOT. You can fix adb autostart either by installing "ADB Root" magisk module or by disabling this module.
Download v1.0: https://github.com/evdenis/enable_eng/releases/download/v1.0/enable_eng.zip
Source code: https://github.com/evdenis/enable_eng
Support: Telegram
Kexec tools for Android
This module adds statically linked kexec binary to your system. Aarch64 only. Kexec is a system call that enables you to load and boot into another kernel from the currently running kernel. Your kernel should support kexec.
Download v1.0: https://github.com/evdenis/kexec/releases/download/v1.0/kexec.zip
Source code: https://github.com/evdenis/kexec
Support: Telegram
GDISK/Parted for Android
The module adds statically linked parted/sfdisk/fdisk/gdisk binaries to your system. Aarch64 only. These utils are standard linux tools to edit the partitions tables on disks.
Download v2.0: https://github.com/evdenis/disk/releases/download/v2.0/disk-v2.0.zip
Source code: https://github.com/evdenis/disk
Support: Telegram

Is also valid for One Plus 5 ?
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

tmviet said:
Is also valid for One Plus 5 ?
Click to expand...
Click to collapse
Hi, these magisk modules are device independent. Yes, you can use them on One Plus 5.

evdenis said:
Hi, these magisk modules are device independent. Yes, you can use them on One Plus 5.
Click to expand...
Click to collapse
Tks. A lot [emoji6]
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

Thanks @evdenis, this module is great! I haven't gotten the 100% desired behavior (getting adbd with actual root perms) because I'm running a 32-bit architecture (armeabi-v7a) and you've supplied only the 64-bit version of adbd, but I've been using your module to swap out 32-bit versions of different versions of adbd I have lying around (older devices). I'm a n00b when it comes to building adbd from scratch using the latest sources with your patch so I'm planning on using the adbd that came with the device and using a disassembler and a hexeditor to NOP out some calls, such as the call to minijail_enter() and see if I have any success. The original device version of adbd doesn't seem to have the functions in it that you built with the patch, but instead appears to use a bunch of minijail library functions. The device is a rooted android 8.1.0 OS, but it is only rooted systemlessly so many of the ro.* build properties affecting adb are changed well after the OS-essential portion boots rendering my efforts thus-far using the original adbd ineffective I'm guessing. I can now issue the "adb root" command from my machine, but adbd on the device is always being launched with the following command line arg "--root_seclabel=u:r:su:s0" and never gains root permissions by default (the behavior I'm trying to achieve). I can manually use "su" but this doesn't help me with push/pull requests to protected parts of the OS and chainfire's "ADB Insecure" patches adbd successfully, but I still don't get the root perms.
Do you know if the system is starting the process with reduced permissions (i.e. adbd will never be able to gain root access on its own no matter what I modify) and I should go a different route like modifying something else in the system rather than adbd? Again, I've already modified the ro.* properties affecting adbd so it does attempt to re-launch itself as root, it just doesn't end up getting the root perms. Manually launching adbd after killing it from within a shell on the device doesn't seem to affect the permissions in ultimately gets.
If you are anyone has any insight as to what I need to do so that adbd gains root permission, that would be much appreciated.

bpaxda said:
I'm planning on using the adbd that came with the device and using a disassembler and a hexeditor to NOP out some calls, such as the call to minijail_enter() and see if I have any success.
Click to expand...
Click to collapse
It was my initial attempt to gain "adb root" on samsung s10. And noping a couple of calls is not enough on the phone. adbd binary on your device could be compiled without "adb root" branch. This is the case on samsung s10. If "adb root" branch exists one need to force should_drop_privileges() function to return false (https://android.googlesource.com/platform/system/core/+/refs/heads/master/adb/daemon/main.cpp#65) in order to get into the "adb root" branch of code (https://android.googlesource.com/platform/system/core/+/refs/heads/master/adb/daemon/main.cpp#151).
bpaxda said:
ro.* build properties affecting adb are changed well after the OS-essential portion boots rendering my efforts thus-far using the original adbd ineffective I'm guessing.
Click to expand...
Click to collapse
You could try enable_eng magisk module (https://github.com/evdenis/enable_eng). The module changes ro.* props to engineering build props. Depending on a firmware this could help to get "adb root". However, no guaranties that the module will not softbrick your device. In case of softbrick you will need to reboot to TWRP and delete the module, instruction is in the README.md.
bpaxda said:
I can now issue the "adb root" command from my machine, but adbd on the device is always being launched with the following command line arg "--root_seclabel=u:r:su:s0" and never gains root permissions by default (the behavior I'm trying to achieve).
Click to expand...
Click to collapse
Try to disable SELinux either with the magisk module or with a script.

Thanks for your response.
I think you're right. Despite having adjusted the ro properties post-boot, there was nothing in ADB that would change the privileges as if it has been compiled out. By sheer luck, I managed to grab adbd from an identical device that had a recent forced firmware update, but the "improved adbd" actually let me get closer. The updated adbd had code changes to its adbd_main function so that it at least looks at the properties "ro.secure" and "service.adb.root" not to mention new calls to minijail_capbset_drop(), minijail_change_gid() and minijail_change_uid(). Using magisk to dynamically replace my original adbd binary with this updated one actually worked in getting adbd to start root shells without needing to invoke "su"!
However its a weird type of root that can't read certain files like /verity_key but I can see some things I should be able to see as root. I'm no SELinux expert, but my guess is that if everything is functioning correctly, I may be getting an SELinux "restricted" root. In this case, it might be the most I can expect from an SELinux enabled kernel launching adbd as root. Let me explain: since I'm using Magisk, post-boot systemlessly, (the system boots restricted and then I use the mtk_su exploit, to gain root and disable permissive SELinux mode), I'm getting permissive root on a session by session basis. I think the nature of this type of root means the kernel is probably still locked down and thus whatever daemon may be responsible for launching adbd remains locked down. Does this sound correct to you? If so, I can live with that
I'd love to get TWRP on this device, but I'm not sure its possible since TWRP doesn't list my device as supported on their website nor can I get into fastboot mode (I didn't try that hard because I wanted to exhaust other options before flashing anything). Do you think enable_eng would work *after* the ACTION_BOOT_COMPLETE event is processed? I.e. my device is rooted after bootup by a script which runs the exploit, but it is well after the system is fully running and locked-down. Luckily Magisk has a utility to change ro properties, but some of those properties are not looked-at by the system this late in the boot stage. Do you think in this case "enable_eng" would work for me? Thanks again!

bpaxda said:
Let me explain: since I'm using Magisk, post-boot systemlessly, (the system boots restricted and then I use the mtk_su exploit, to gain root and disable permissive SELinux mode), I'm getting permissive root on a session by session basis.
Click to expand...
Click to collapse
I'm not sure that my modules will work with this rooting scenario. As far as I could understand, magisk by default replaces the init process, patches selinux policy before it is loaded and next, calls the original init binary. I don't think that it will be possible to alter selinux policy with different boot scenario for magisk.
bpaxda said:
Do you think enable_eng would work *after* the ACTION_BOOT_COMPLETE event is processed? I.e. my device is rooted after bootup by a script which runs the exploit, but it is well after the system is fully running and locked-down. Luckily Magisk has a utility to change ro properties, but some of those properties are not looked-at by the system this late in the boot stage. Do you think in this case "enable_eng" would work for me?
Click to expand...
Click to collapse
I'm not sure that enable_eng will work. adbd daemon check some properties such as ro.secure dynamically, but they could be cached after the boot. I don't know the ways to drop the cache and re-read these properties (altered with magisk) after the boot. Here are the main properties the modules changes https://github.com/evdenis/enable_eng/blob/master/system.prop

Thanks for making this tool! I'm just wondering if I need to modify my adb to use the module - I run "adb root" normally and get "adbd cannot run as root in production builds" still

Anyone know why when i install SELinux Permissive version 2.0 of the module it still states version 1 in Magisk?

I flashed this in Magisk and rebooted. Now my phone is stuck in a boot loop. Any ideas? I'm using Sony Xperia XZ1 compact.

cheeklitched said:
I flashed this in Magisk and rebooted. Now my phone is stuck in a boot loop. Any ideas? I'm using Sony Xperia XZ1 compact.
Click to expand...
Click to collapse
If you have twrp installed just uninstall and reinstall magisk.
Otherwise,
Boot to bootloader and flash your boot.img file
Code:
fastboot flash boot boot.img
Then let phone boot. Reboot to bootloader again. Flash magisk_patched.img
Code:
fastboot flash boot magisk_patched.img
During startup, as soon as you get to the Google logo, hold the volume button down. This should start the phone in safe mode. See if it loads. If not, reboot phone, and execute this in terminal/command prompt:
Code:
adb wait-for-device shell magisk --remove-modules
This should allow the phone to start up all the way. Enable whatever modules you want. You may need to flash magisk_patched.img again.
This has fixed multiple problems for me. It's redundant, but it tends to work.

I installed the Magisk selinux script, but after installing it no longer shows in Magisk, so how do I dissable/undo/uninstall the script? I installed a Selinux checker and it says it is on permissive, so the scrip must have installed, but I want to remove it. Is there an undo script, or can I manually delete the script in my root filesystem? THX

Hello guys
I used Redmi K20 pro with Eu rom 10.4, android 10.
I used the lastest version of this module but my devices was not found on ADB system on my computer.
So what I do now? I tried to fix it but I cannot find anything about it.

Recently, setting SElinux to permissive is not advised. I had a issue with V4A setting my SElinux to permissive permenantly, but editing the magisk module to set SElinux to enforcing instead of permissive also works.
This is probs the only module that actually sets SElinux properly.
Here's the modded magisk module with the same credited creator, but just sets SElinux to Enforcing instead of permissive

OMFG I THINK THIS IS WHAT IVE BEEN LOOKING FOR. TEH HOLY GRAILLLLL OMGOMGOMG THANK YOU THANK YOU THANK YOUUUUU

Will ADB Root work for Android 8.1?

evdenis said:
These modules are not meant for everyday use. They are intended for debugging and modification of a firmware. They significantly lower security of your device while active and even could softbrick it. You've been warned.
ADB Root
Magisk Module that allows you to run "adb root". adb root is not an ordinary root (su), it's adbd daemon running on your phone with root rights. adb root allows you to "adb push/pull" to system directories and run such commands as "adb remount" or "adb disable-verify".
Download v1.0: https://github.com/evdenis/adb_root/releases/download/v1.0/adb_root.zip
Source code: https://github.com/evdenis/adb_root
Support: Telegram
SELinux Permissive
This module switches SELinux to permissive mode during boot process. This module intentionally lowers security settings of your phone. Please don't use it if there is a better solution to your problem, e.g., magiskpolicy. The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels.
Download v2.0: https://github.com/evdenis/selinux_permissive/releases/download/v2.0/selinux_permissive_v2.0.zip
Source code: https://github.com/evdenis/selinux_permissive
Support: Telegram
Enable Eng
This Magisk Module enables engineering build props. It allows to activate debugging parts of a firmware. Please, disable Magisk Hide for this module. If you don't know what you are doing, don't use this module. It can easily softbrick your device.
Troubleshooting
If your device doesn't boot then you need to reboot to TWRP recovery and
Code:
$ adb shell rm -fr /data/adb/modules/enable_eng
If ADB doesn't work that means adbd in your firmware is build without ALLOW_ADBD_ROOT. You can fix adb autostart either by installing "ADB Root" magisk module or by disabling this module.
Download v1.0: https://github.com/evdenis/enable_eng/releases/download/v1.0/enable_eng.zip
Source code: https://github.com/evdenis/enable_eng
Support: Telegram
Kexec tools for Android
This module adds statically linked kexec binary to your system. Aarch64 only. Kexec is a system call that enables you to load and boot into another kernel from the currently running kernel. Your kernel should support kexec.
Download v1.0: https://github.com/evdenis/kexec/releases/download/v1.0/kexec.zip
Source code: https://github.com/evdenis/kexec
Support: Telegram
GDISK/Parted for Android
The module adds statically linked parted/sfdisk/fdisk/gdisk binaries to your system. Aarch64 only. These utils are standard linux tools to edit the partitions tables on disks.
Download v2.0: https://github.com/evdenis/disk/releases/download/v2.0/disk-v2.0.zip
Source code: https://github.com/evdenis/disk
Support: Telegram
Click to expand...
Click to collapse
how can i make permissive enfocing because in 2022 i heard thats a BIG security risk and my custom ROM (havoc os) if selinux permissive

Why doesn't Magisk repo just add Magisk binaries to his releases?

Yea,
i mean that them would be usefull. it costs nothing to add them in a zip in releases tab.
Else everytime a new magisk release comes out i need to compile them...
Also is there a difference on using the same folder (arm64-v8a) on any phone or does every phone have custom folder (x86_64, x86, arm64-v8a or armeabi-v7a)?

Quark Thonos said:
Yea,
i mean that them would be usefull. it costs nothing to add them in a zip in releases tab.
Else everytime a new magisk release comes out i need to compile them...
Also is there a difference on using the same folder (arm64-v8a) on any phone or does every phone have custom folder (x86_64, x86, arm64-v8a or armeabi-v7a)?
Click to expand...
Click to collapse
John Wu only develops Magisk - that's it. There's a reason why he doesn't bundle any modules with Magisk, although I forget what it is.
I'm not sure what you mean by "folder" but you need to use the appropriate architecture for your device. Most are arm64.

Yes, i solved architecture issue...
Just asking why binaries cannot be included with the releases...

Also, i am working on boot_patch.sh script but i need to know when to use these parameters :
KEEPVERITY, KEEPFORCEENCRYPT, PATCHVBMETAFLAG, RECOVERYMODE
i know when to use KEEPFORCEENCRYPT by just checking "adb shell getprop | find 'ro.crypto.state'"
PATCHVBMETAFLAG just check if vbmeta.img exists (right?)
and KEEPVERITY just in boot.img headers
same for RECOVERYMODE for ramdisk right?