[KernelSU][Android13.0][NX563J] - ZTE Nubia Z17 ROMs, Kernels, Recoveries, & Other

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KernelSU for Nubia Z17 Based on Android 13
Overview of KernelSU
KernelSU is working in Linux kernel mode, it has more control over userspace applications.
Only App that is granted root permission can access `su`, other apps cannot perceive su.
KernelSU supports modify /system systemlessly by overlayfs, it can even make system writable.
More information: KernelSU Official Website
If you do not use modules or only use simple modules, KernelSU is not detected by default. You don't need to worry about hiding root, because the default is hiding.
(As shown in Figure 3, "Zygisk on KernelSU" module will let you loss hidden root.)
Choose one of the two download methods
Download(Github release)(stable)
Kernel HERE (Include a default one and a permissive one for GSI user)
Manager APK HERE (just download apk like this KernelSU_v0.5.7_10866-release.apk)
Notice that: I tested the Github release kernel and I wrote the system I used.
Please use the same system
(Optinal, but if you have bug may be your system is not match to my kernel)
Download(not recommend)(GitHub actions)(latest)
Kernel HERE
Manager APK HERE
Install Guide
Backup your boot.img, If something wrong, flash your original boot.img. You can get it in /dev/block/by-name/boot or your ROM.zip.
For nubia z17 (nx563j), It may work on
LineageOS 20.0(may work)
PixelExperiencePlus13(I tested)
other ROMs based on LineageOS 20.0 kernel(may work)
Use TWRP flash the kernel(boot.img) given by me.
OR use "fastboot flash boot boot.img" flash the kernel(boot.img) given by me.
Install the KernelSU's manager.apk.
Enjoy it.
Thanks
LineageOS Project
KernelSU Official Website
BugReport
@Dispossible
酷安@霁月难逢彩云亦散

sorry can i get a link to directly downloading?

and also for manager ...

and [email protected] ......
would also thank you ...

don't know why my old member name is now shown..0157horst you know

0157horst said:
sorry can i get a link to directly downloading?
Click to expand...
Click to collapse
I will add a easier download guide

Dispossible said:
I will add a easier download guide
Click to expand...
Click to collapse
maybe a new hoster not git you know

0157horst said:
maybe a new hoster not git you know
Click to expand...
Click to collapse
Add sourceforge download link.

How do you install the lsposed module? Like magisk but flash in kernelsu?

dd805bb said:
How do you install the lsposed module? Like magisk but flash in kernelsu?
Click to expand...
Click to collapse
As shown in figure 3.
Use zygisk on kernelsu https://github.com/Dr-TSNG/ZygiskOnKernelSU/releases
And lsposed on zygisk (zygisk version) (not riru) https://github.com/LSPosed/LSPosed/releases

Dispossible said:
As shown in figure 3.
Use zygisk on kernelsu https://github.com/Dr-TSNG/ZygiskOnKernelSU/releases
And lsposed on zygisk (zygisk version) (not riru) https://github.com/LSPosed/LSPosed/releases
Click to expand...
Click to collapse
Do you get a systemless host module running? Looking for how to get Adaway up and running.

dd805bb said:
Do you get a systemless host module running? Looking for how to get Adaway up and running.
Click to expand...
Click to collapse
Maybe the same as Magisk. I install a host module to prevent MIUI update, it just for test. I just copy a module randomly from another phone.

Is it also work on OneUI 5.1? I have that kernel name: 5.15.41-android 13-8-25800099-abS918BXXU1AWC8 #1 Fri Mar 24 09:14:54 UTC 2023
My device is Samsung Galaxy S23 Ultra
Thanks in advance

dd805bb said:
Do you get a systemless host module running? Looking for how to get Adaway up and running.
Click to expand...
Click to collapse
Have you found a solution?

nicky-xda said:
Have you found a solution?
Click to expand...
Click to collapse
Module for KSU

@dd805bb @nicky-xda @theoneofgod
Here is the same module as in the picture.
download and edit /system/etc/hosts in the module, and install the module.

RealMooni said:
Is it also work on OneUI 5.1? I have that kernel name: 5.15.41-android 13-8-25800099-abS918BXXU1AWC8 #1 Fri Mar 24 09:14:54 UTC 2023
My device is Samsung Galaxy S23 Ultra
Thanks in advance
Click to expand...
Click to collapse
Releases · tiann/KernelSU
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
go to this release link.
download the AnyKernel3-android13-5.15.78_2022-05.zip this one. and use TWRP to flash it.

请教:刷谷歌官方的GSI:gsi_gms_arm64-exp-UPB2.230407.014.A1-10066424-22683335 ,也会出现开机红色警告,为什么?
Ask: Google official GSI: gsi_gms_arm64-exp-UPB2.230407.014.A1-10066424-22683335, there will be a red warning when booting, why?

Tims Fong said:
请教:刷谷歌官方的GSI:gsi_gms_arm64-exp-UPB2.230407.014.A1-10066424-22683335 ,也会出现开机红色警告,为什么?
Ask: Google official GSI: gsi_gms_arm64-exp-UPB2.230407.014.A1-10066424-22683335, there will be a red warning when booting, why?
Click to expand...
Click to collapse
我也不知道,你动boot分区了吗?这个boot开其他系统可以吗?
I don't know. Do you edit the boot partition?This boot partition can boot other GSI rom?

Dispossible said:
我也不知道,你动boot分区了吗?这个boot开其他系统可以吗?
I don't know. Do you edit the boot partition?This boot partition can boot other GSI rom?
Click to expand...
Click to collapse
这个文件boot_permissive,只要是A13 phh GSI,都可以起到permissive的作用,且不会出现开机红色警告。对于Nippon GSI和谷歌A14 GSI,没有刷这个文件,也会出现开机红色警告,我想这个与permissive无关。
This file boot_permissive, as long as it is A13 phh GSI, can play the role of permissive, and there will be no red warning when booting. For Nippon GSI and Google A14 GSI, if this file is not flashed, there will be a red warning when booting up. I think this has nothing to do with permissive.

Related

[RECOVERY] TWRP 3.3.1-0 (lilac) [UPDATE: 2019-09-16]

TWRP
This project provides the TWRP recovery for for the Sony Xperia XZ1 Compact (lilac).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEATURES
File-Based Encryption (FBE) support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
This recovery will use the security patch level from the system partition to decrypt data. It should not be tied to a security patch level anymore.
DOWNLOAD
Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!
You can always find the latest version of the recovery HERE.
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img and recovery.img.asc.txt file
Rename the recovery.img.asc.txt file to recovery.img.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!​
XDA:DevDB Information
recovery_twrp_sony_lilac, Tool/Utility for the Sony Xperia XZ1 Compact
Contributors
modpunk, Dees_Troy
Source Code: https://github.com/cryptomilk/android_device_sony_lilac
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-09-16
Created 2017-11-18
Last Updated 2019-09-16
Nice work!
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
4rz0 said:
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Click to expand...
Click to collapse
RTFM!
aikon96 said:
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
Click to expand...
Click to collapse
No, I need to create one for November. Will do that soon.
modpunk said:
RTFM!
Click to expand...
Click to collapse
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
4rz0 said:
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
Click to expand...
Click to collapse
There is no limitation in flashing. However there is no LOS you can flash yet ...
works perferct! thank you :good:
I got an XZ1. Any chance to get TWRP for it (for testing)?
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
TWRP
modpunk said:
Could someone please test
Click to expand...
Click to collapse
ok. I'll test it
modpunk said:
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
Click to expand...
Click to collapse
I will indeed test too juhuuu...
it flashes okay via fastboot, and twrp is also working. except for format option under wipe, when typing 'continue' it seems like it doesn't show the inputs, only the last letter 'e'
anyway after i flashed the twrp, i booted it up, and mounted everything except for otg. and then of course i flashed magisk.zip (latest v14) and it also succeeded
but then when i reboot from twrp, it stucks at sony logo, meaning default bootanimation doesn't kick in, and i patiently waited for like 10-15 min
so i assume it's not working. i even tried with a userdebug and regular user build 47.1.A.5.51
now i will try just to boot the twrp without flashing it and then flash magisk.zip while it's booted up via fastboot to see if it boots up normally
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
modpunk said:
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
Click to expand...
Click to collapse
A: it does not ask for password upon bootup so i guess it's not encrypted in that way
B attached here
C is there any specific logcat you want, like error or fatal level etc.
Question just to be clear: do we have to update twrp for evry new securitypatch?
To decrypt the /data partion on a stock ROM, yes you do.
Hi modpunk,
Ur a true star...****
I just want to ask a couple of question's.
Does the bootloader have to be unlocked in order to flash this....?
I have had a Z3 Compact and got it rooted with bootloader locked and also a Z5 Compact using munjen setup.
Install TWRP on it Flashed SuperSU using TWRP was best thing i did.
Do you have a step by step guide how to flash this. I would love to test it for you.
When you flash is it using munjen flashtool...?
Thanks Sham
UPDATE
TRWP is working actually, just figured out that it's magisk that get the phone not to boot, bith 14 and 14.5
and latest supersu both the xperia one and the regular one v.2.82 fails, give error "unzip fail, no proper recovery etc."
Now for fun i will load it up with userdebug firmware and see if i can make it manually root with the "angela" method

[CLOSED] [G97X] SoLdieR9312s G97X AROMA MOD ZIP || 4.0 | Android 9.0 | ASG8 | 27/07

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Support for SM-G970F/FD, SM-G973F/FD, SM-G975F/FD
N-Device Models are not supported because of OXM CSC Partition
always based on latest Security Patch Base
disables vaultkeeper, frp, secure storage, file based encryption on /data (@ianmacd)
decrypted CSC Partition included for CSC Feature mods
Removes Knox and other Security related Stuff
build.prop Tweaks
App Debloating
Emoji Changer
Font Changer
Bluetooth Force aptX Codec
Activate Multiuser support
Install Good Lock apps
Bixby Button remap
CSC Feature Options
Always latest Version
[INT] Telegram Support Chat
SVN Repository
Flash zip in TWRP and follow AROMA Installer Instructions
Code:
Please do not take anything without asking us first. We will 99% allow you to use anything, just ask first though.
You cannot use any of our work which hasn't been released in an official ROM release unless given express permission.
We are not responsible for anything that happens to your device while using this ROM.
By using this ROM you agree with the above terms.
XDA:DevDB Information
[G97X] SoLdieR9312s G97X AROMA MOD ZIP || 4.0 | Android 9.0 | ASG8 | 27/07, Tool/Utility for the Samsung Galaxy S10
Contributors
SoLdieR9312
Version Information
Status: Stable
Current Stable Version: 4.0
Stable Release Date: 2019-07-27
Created 2019-04-05
Last Updated 2019-07-27
Reserved
Reserved
Finally
Great , you are the best
Now we have to wait for trwp to flash it
That was quick. Congratulations @SoLdieR9312s !
Wowsers Soldier is marching on....... but it's a tease until twrp is made public.....
Cross my fingers for Sunday (...)
Soldier, are you teasing a future release of TWRP and root? I love you bro, great works on my N9. Good to see you here
Kudos! Let's Rock
Thanks man, waiting for your S10 rom!
sayou94 said:
Soldier, are you teasing a future release of TWRP and root? I love you bro, great works on my N9. Good to see you here
Click to expand...
Click to collapse
Never have done anything for N9^^
jjow said:
Thanks man, waiting for your S10 rom!
Click to expand...
Click to collapse
I don't do a full rom release anymore, just the mod zip to flash on stock odin files^^
SoLdieR9312 said:
Never have done anything for N9^^
Click to expand...
Click to collapse
Sorry, i had N9 and S9+ both, i probably used your rom on S9+
Have this been tested with magisk? Do you think it may be possible to add magisk as an aroma option? Or is that just wishful thinking?
E.
X
EMB95 said:
Have this been tested with magisk? Do you think it may be possible to add magisk as an aroma option? Or is that just wishful thinking?
E.
X
Click to expand...
Click to collapse
You cannot flash magisk in stock recovery. And even if you have TWRP patched with Magisk, you cannot flash magisk in twrp. You need to update Magisk with Manager.
As TWRP will be prerooted with Magisk or when you patch it once, no need to add Magisk in any zips. You reboot to rooted system and done.
Please read the Magisk Instructions to understand how it's going on the 10 series.
SoLdieR9312 said:
You cannot flash magisk in stock recovery. And even if you have TWRP patched with Magisk, you cannot flash magisk in twrp. You need to update Magisk with Manager.
As TWRP will be prerooted with Magisk or when you patch it once, no need to add Magisk in any zips. You reboot to rooted system and done.
Please read the Magisk Instructions to understand how it's going on the 10 series.
Click to expand...
Click to collapse
Sorry for being a little dense but to clarify:
If one is to flash your 'Rom' over stock S10, one first roots as per instructions for Magisk,
then boot to Recovery by long-holding Vol Up button, flash your zip and then finally boot to 'System with Magisk'?
Norup58 said:
Sorry for being a little dense but to clarify:
If one is to flash your 'Rom' over stock S10, one first roots as per instructions for Magisk,
then boot to Recovery by long-holding Vol Up button, flash your zip and then finally boot to 'System with Magisk'?
Click to expand...
Click to collapse
Hoping I get this correct from soldier in Telegram chat but no, you can't use his modpack until another variant of rooting comes along, via twrp.
John's implementation just doesn't disable some crucial things as the other variant will.
1.2 released
added device check for build.prop stuff
fully fixed app debloating
added aroma option to replace Warning splash screens
added Samsung Digital Wellbeing to Aroma debloat option
added Secure Wifi and SecureFolder to always remove list
added Bixby Routines to Bixby debloat option
SoLdieR9312 said:
1.2 released
-app debloating finally working without issues
-added aroma option to replace the ugly warning splash screens
Click to expand...
Click to collapse
No one got to try V1.1 .......

[CLOSED][ROM][Pie - 9.0.0_r45][OFFICIAL - 07/26/2019] StatiXOS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WE NOW HAVE AN OFFICIAL TELEGRAM GROUP - StatiXOS @ Telegram​
Features
Right now you are gonna find a mixed StatiX/AOSP experience as this is a brand new project:
Spark Settings Panel introduced.
Always-On Display
Advanced reboot
Dark mode and accent theming
Statusbar battery styles
Quick unlock
SELinux Enforcing
Q Features
Upstreamed to latest Linux stable
There's obviously more, but I'm not gonna list every one. Flash and find out!
Known Issues:
Squeeze sensitivty is reversed. This will be fixed at some point, but not something that's exactly high priority.
Installation:
Flash using TWRP.
First, factory reset.
Flash ROM
Reboot and enjoy
Downloads
Jenkins will upload to here.
Notes[/SIZE]
This will be the release cycle.
Nuclear updates are builds are signed with test-keys and will be released bi-weekly/weekly. These may also include some changes from our Gerrit found at https://review.statixos.me/ or changes I am personally testing.
Official builds will come monthly with each sec patch and will be signed with release keys using our build server. These will be a fresh repo sync with no changes.
Credits
Code:
Dirty Unicorns
ABC Rom
AmyClaraRose
argraur
beanstown106
CarbonROM
ezio84
Greg Kroah-Hartman
kantjer
Mazda
nardow
NexusPieX
Google
LineageOS
simarguram
skiman10
XDA:DevDB Information
StatiXOS, ROM for the Google Pixel 3a
Contributors
[URL="https://forum.xda-developers.com/member.php?u=7299508"]ZVNexus
Source Code: https://github.com/StatiXOS/android_device_google_sargo
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: July Vendor Image
Based On: AOSP
Version Information
Status: Beta
Current Stable Version: 2.1
Current Beta Version: 2.1
Beta Release Date: 2019-06-18
Created 2019-06-18
Last Updated 2019-07-26
Looks nice! Thanks for the build! Keep up the great work.
Sent from my Pixel 3a using Tapatalk
NICE!
And happy to read that you're working on TWRP!
Finally some dev work on the Pixel 3a! Thank you!!!!!!!!!
dope ..thx
where is pru dev Anay..lol
Uploading new build right now with just the regular P3A boot animation, and with Google Camera.
Do I need to update to the June stock firmware first? Or can I flash over March?
prenedo said:
Do I need to update to the June stock firmware first? Or can I flash over March?
Click to expand...
Click to collapse
Read the OP!
prenedo said:
Do I need to update to the June stock firmware first? Or can I flash over March?
Click to expand...
Click to collapse
You need the June firmware/vendor, don't know what happens if you don't. I just know its enough of a difference that TWRP works with march blobs but not with June blobs.
Absolutely awesome thank you OP
Does this have the camera found in stock ROM, with all of the features (eg night sight)?
Thanks
GQJ said:
Does this have the camera found in stock ROM, with all of the features (eg night sight)?
Thanks
Click to expand...
Click to collapse
Yep!
Can we see some screenshots?
prempremprem said:
Can we see some screenshots?
Click to expand...
Click to collapse
Looks like stock, just less bloatware. Google apps like gmail and chrome also aren't included. Not a big deal just pointing it out.
So I tried to root this thin using the @PBandJ method. But instead of grabbing the stock boot.img and patching that through Magisk, I grabbed this ROM's boot.img and did the same thing. I was able to flash the .img and reboot with no problem...but Magisk still shows that it isn't installed and I am not rooted. Not sure what's wrong here?
stevew84 said:
So I tried to root this thin using the @PBandJ method. But instead of grabbing the stock boot.img and patching that through Magisk, I grabbed this ROM's boot.img and did the same thing. I was able to flash the .img and reboot with no problem...but Magisk still shows that it isn't installed and I am not rooted. Not sure what's wrong here?
Click to expand...
Click to collapse
Those root threads are for stock.
Since this is a custom ROM the boot image is probably already modified to accept Magisk modifications or it is already rooted. So, did you try just a direct install from the Magisk manager app?
Choosing < Direct Install (recommend) > without any fastboot flashing or or any other actions?
12paq said:
Those root threads are for stock.
Since this is already a custom ROM the boot image is probably already modified to accept Magisk modifications. So, did you try just a direct install from the Magisk manager app?
Choosing < Direct Install (recommend) > without any fastboot flashing or or any other actions.
Click to expand...
Click to collapse
I downloaded the Magisk manager and the only option to install Magisk is the .zip...but I'm not sure how to install a zip without TWRP. I would usually use an app but since I'm not rooted I can't.
stevew84 said:
I downloaded the Magisk manager and the only option to install Magisk is the .zip...but I'm not sure how to install a zip without TWRP. I would usually use an app but since I'm not rooted I can't.
Click to expand...
Click to collapse
Hmmm.. ok. Time for the OP to chime in and comment and hopefully answer this.
12paq said:
Hmmm.. ok. Time for the OP to chime in and comment and hopefully answer this.
Click to expand...
Click to collapse
Right. I know what I'm doing and I've been around Android since like 2010, but this just isn't working. I haven't gotten the nerve to actually fastboot flash the zip file for Magisk yet.
stevew84 said:
Right. I know what I'm doing and I've been around Android since like 2010, but this just isn't working. I haven't gotten the nerve to actually fastboot flash the zip file for Magisk yet.
Click to expand...
Click to collapse
I know the feeling! Frustrating and fun to troubleshoot at the same time. Haha
On more question. Did you have the have the Edge Sense module installed prior to flashing the ROM?

General KernelSU works fine on OnePlus11. You can get root.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
isn't it yet to be sold and aquired?
more_than_hater said:
isn't it yet to be sold and aquired?
Click to expand...
Click to collapse
I believe it is out in China already
JPower123 said:
I believe it is out in China already
Click to expand...
Click to collapse
Yes, it is out in China and launching on Feb 7 here in India! I'm interested in this phone...
Wasim_Bu said:
Yes, it is out in China and launching on Feb 7 here in India! I'm interested in this phone...
Click to expand...
Click to collapse
What about USA? EU?
luckychukiye said:
What about USA? EU?
Click to expand...
Click to collapse
Pretty sure it's also Feb 7 for USA, not sure about EU, but probs same
I am also waiting for India, to install OOS.
What is kernelSU? I'm wondering if Magisk works on it, it SHOULD being that it's just a patched boot image. But I'm curious to know
H4X0R46 said:
What is kernelSU? I'm wondering if Magisk works on it, it SHOULD being that it's just a patched boot image. But I'm curious to know
Click to expand...
Click to collapse
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
luckychukiye said:
What about USA? EU?
Click to expand...
Click to collapse
It's launching on Feb 7th for USA and UK!
huangsijun17 said:
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
A new root solution? Does Magisk not work on the OnePlus 11 or are they both viable options? I'm confused now.
H4X0R46 said:
A new root solution? Does Magisk not work on the OnePlus 11 or are they both viable options? I'm confused now.
Click to expand...
Click to collapse
A new root solution, can run with Magisk at the same time.
Because when I just got the phone, there was no TWRP and ZIP flashing package. I'm having a hard time installing Magisk directly. But after I gave Magisk Manager Root permission with KernelSU, I installed Magisk directly.
huangsijun17 said:
A new root solution, can run with Magisk at the same time.
Because when I just got the phone, there was no TWRP and ZIP flashing package. I'm having a hard time installing Magisk directly. But after I gave Magisk Manager Root permission with KernelSU, I installed Magisk directly.
Click to expand...
Click to collapse
When you root with magisk. You need to unlock the bootloader. Then install magisk manager app. Pull your stock boit.img from stock firmware and put it on phone. Open magisk manager and select install then patch boot.img . Then copy the generated image magisk patched image to computer adb folder. Then reboot phone to fastboot. On computer type fastboot boot (name of patched boot.img).img phone will reboot and have root. Go back to magisk and select direct install then reboot.
toolhas4degrees said:
When you root with magisk. You need to unlock the bootloader. Then install magisk manager app. Pull your stock boit.img from stock firmware and put it on phone. Open magisk manager and select install then patch boot.img . Then copy the generated image magisk patched image to computer adb folder. Then reboot phone to fastboot. On computer type fastboot boot (name of patched boot.img).img phone will reboot and have root. Go back to magisk and select direct install then reboot.
Click to expand...
Click to collapse
No. I never exported boot.img or boot_init.img from my phone. There is also no unpacking payload.bin to extract them. After installing KernelSU and KernalSU Manager, I use KernelSU to give Magisk Manager a root privilege. Magisk Manager will automatically install Magisk.
In addition, Magisk needs to patch boot_init.img in devices pre-installed with Android 13, and the flash command is also fastboot flash boot_inti boot_init.img.
huangsijun17 said:
View attachment 5804063
Click to expand...
Click to collapse
Hi,
can you pleaaase try this app if it works with root or no??
CIB Egypt Mobile Banking - Apps on Google Play
The CIB Mobile Banking app is designed to meet all your banking needs.
play.google.com
loshabih said:
Hi,
can you pleaaase try this app if it works with root or no??
CIB Egypt Mobile Banking - Apps on Google Play
The CIB Mobile Banking app is designed to meet all your banking needs.
play.google.com
Click to expand...
Click to collapse
Three interfaces: GKI supported, GKI not supported and already installed. In addition, for devices that do not support GKI, it is also possible to compile the kernel yourself.
huangsijun17 said:
View attachment 5811645
View attachment 5811647View attachment 5811651
Three interfaces: GKI supported, GKI not supported and already installed. In addition, for devices that do not support GKI, it is also possible to compile the kernel yourself.
Click to expand...
Click to collapse
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
loshabih said:
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
Click to expand...
Click to collapse
I installed Magisk and KernelSU at the same time, so I can't test the APP for you. But in theory, KernelSU uses a whitelist system, and unauthorized software cannot detect the existence of the su file.
loshabih said:
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
Click to expand...
Click to collapse
For devices that support GKI 2.0, you can directly download the corresponding version of boot.img from Github Action to flash in.
huangsijun17 said:
I installed Magisk and KernelSU at the same time, so I can't test the APP for you. But in theory, KernelSU uses a whitelist system, and unauthorized software cannot detect the existence of the su file.
Click to expand...
Click to collapse
can you lock the bootloader while you have kernelSU? as the app is checking the bootloader status?

[ROM][UNOFFICIAL][13][nx563j] Pixel Experience Plus 13 for Nubia Z17

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel Experience Plus 13 for Nubia Z17
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation).
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device.
What works?
Audio
Bluetooth
Botton backlight controll
Calls/SMS/Mobile data
Camera (Photo/Video/Flashlight)
DT2W
Fingerprint sensor
GPS
IR Control
NFC
Notification LED
Torchlight
Wifi
Selinux enforce
Issues
You tell me
Download
https://sourceforge.net/projects/kindle4jerry-rom/files/nx563j/peplus-13/
https://www.123pan.com/s/Zp0lVv-FWfk3
(The same file, use which link depends on your network)
Install Guide
Download the ROM zip
Install a compatible Recovery (TWRP Recovery)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash PixelExperience Plus
Reboot
Latest version
notice: If you encounter a double-layer status bar after updating, please delete /data/user_de/0/com.android.systemui and reboot.
2023-06-19 good, help me test it. (But not June security patch, may be several days later)
2023-05-24 2023-04-03 2023-03-15 No NFC.
2023-01-30(Not Recommended) BUG: May cause app crash
Source Code
Device Tree https://github.com/kindle4jerry/android_device_nubia_nx563j/tree/pep-13
Device Common https://github.com/kindle4jerry/android_device_nubia_msm8998-common/tree/pep-13
Kernel https://github.com/kindle4jerry/android_kernel_nubia_msm8998/tree/pep-13
Vendor https://github.com/kindle4jerry/android_vendor_nubia-pep
Thanks
@yangcyborg
@BeYkeRYkt
vry good.thank you brother
jep thanks a lot can't wait to try
非常感谢。我想应该会有官方版本。Thank you so much. I think there should be an official version.
very nice my friend nfc is perfectly working and by the way we got 240fps slow motion with this rom and i think also 22.6mp cam with bsg a11v7 snap apk very cool
老大:请教,Z17 不能刷Permissiver_v5,否则开机报错,有办法解决这个问题吗?谢谢。
Boss: Ask, Z17 can't flash Permissiver_v5, otherwise boot up to report an error, is there a way to solve this problem? Thank you.
Tims Fong said:
老大:请教,Z17 不能刷Permissiver_v5,否则开机报错,有办法解决这个问题吗?谢谢。
Boss: Ask, Z17 can't flash Permissiver_v5, otherwise boot up to report an error, is there a way to solve this problem? Thank you.
Click to expand...
Click to collapse
Which ROM? What is Permissiver_v5? Please upload.
aljoscha81 said:
very nice my friend nfc is perfectly working and by the way we got 240fps slow motion with this rom and i think also 22.6mp cam with bsg a11v7 snap apk very cool
Click to expand...
Click to collapse
Which google camera is better?
Dispossible said:
Which ROM? What is Permissiver_v5? Please upload.
Click to expand...
Click to collapse
就是这个补丁。this patch.
Tims Fong said:
就是这个补丁。this patch.
Click to expand...
Click to collapse
I see. Because Z17 need to sign boot.img. If you modify the boot.img. Please use this tool to sign your boot. Use this tools. (I used it on ubuntu x86, I don't know whether it work on windows).
https://github.com/kindle4jerry/boot_signer_for_nubia_nx563j
And I use Github Actions to build kernel and Sign boot.img.
https://github.com/kindle4jerry/KernelSU_Action_nx563j
If it works well, please give me a star.(疯狂暗示)
@Tims Fong
You can try to use some TWRP with sign boot. Such as 绯色_玻璃@weibo.cn.
Now Android removed /system/bin/dalvikvm, some flashable zip boot signer rely on dalvikvm to execute .jar. The boot signer I used is x86 version. So they dont work.
你可以尝试使用带有内核签名功能的TWRP比如之前绯色玻璃做的。
安卓移除了dalvikvm,一些卡刷签名工具依赖dalvikvm来执行jar文件进行签名,所以他们失效了
Dispossible said:
Which google camera is better?
Click to expand...
Click to collapse
i use the one from bsg they working fine for me :https://www.celsoazevedo.com/files/android/google-camera/
maybe arcore/playground is working again i don't test the new update
Dispossible said:
@Tims Fong
You can try to use some TWRP with sign boot. Such as 绯色_玻璃@weibo.cn.
Now Android removed /system/bin/dalvikvm, some flashable zip boot signer rely on dalvikvm to execute .jar. The boot signer I used is x86 version. So they dont work.
你可以尝试使用带有内核签名功能的TWRP比如之前绯色玻璃做的。
安卓移除了dalvikvm,一些卡刷签名工具依赖dalvikvm来执行jar文件进行签名,所以他们失效了
Click to expand...
Click to collapse
绯色玻璃3.2.3可以签名成功,但是不起作用,手机还是报错被锁。另外版本太低,根本就不适应A12/A13.魔趣3.3.1从来就没有签名成功过。
Crimson Glass 3.2.3 can be signed successfully, but it does not work, and the phone is still locked with an error. In addition, the version is too low to adapt to A12/A13.MoKee 3.3.1 has never been successfully signed.
Tims Fong said:
绯色玻璃3.2.3可以签名成功,但是不起作用,手机还是报错被锁。另外版本太低,根本就不适应A12/A13.魔趣3.3.1从来就没有签名成功过。
Crimson Glass 3.2.3 can be signed successfully, but it does not work, and the phone is still locked with an error. In addition, the version is too low to adapt to A12/A13.MoKee 3.3.1 has never been successfully signed.
Click to expand...
Click to collapse
那你就用我给的github那个工具签名
Use the boot signer given above.
by the way to sign boot you have to mount vendor and system manually or am i wrong?
aljoscha81 said:
by the way to sign boot you have to mount vendor and system manually or am i wrong?
Click to expand...
Click to collapse
What is your method? I used x86 PC to sign. Because I dont find TWRP by 绯红玻璃. Several years ago I used 绯红玻璃 but now I dont have it. The TWRP by yangcyborg dont have sign boot functions.
@Tims Fong do you need it to install nippon gsis ?
Dispossible said:
What is your method? I used x86 PC to sign. Because I dont find TWRP by 绯红玻璃. Several years ago I used 绯红玻璃 but now I dont have it. The TWRP by yangcyborg dont have sign boot functions.
Click to expand...
Click to collapse
i take a look i got several twrps from the past got the bootsigner function inbuild i will upload here then you have to test cause i am not at home at the moment
wait few seconds
aljoscha81 said:
i take a look i got several twrps from the past got the bootsigner function inbuild i will upload here then you have to test cause i am not at home at the moment
wait few seconds
Click to expand...
Click to collapse
Thanks
ok twrps are up the second one is from nfound i think but the one from xiu is 100% build in bootsigner i think i can remember that the guy has bring up los 17.1 got also a twrp with build in bootsigner but don't know wich one good luck and let me know what is working for you

Categories

Resources