Related
SkyHigh Kernel -- Ported to SM-G920P (Sprint Galaxy S6).
This is, unquestionably, the most up to date kernel for the S6 devices. That includes upstream kernel (vanilla) additions bringing it to the latest (3.10.108) publicly released. This project started as a port of the SkyHigh kernel, originally by @UpInTheAir, to the G920P kernel. this kernel, however, has a great deal of further enhancements and optimizations relevant to Sprint Galaxy S6 device. The boot image build is not embedded in the kernel sources, as it is in the original, rather is an automated build in a separate project.
Donations:
I do accept donations, you are by no means required to, it just invigorates me to do more stuff in the kernel . With that said, apparently some devices fail to show the donation link next to posts, so you can click here to donate.
DISCLAIMER
Always READ THE DISCLAIMER before engaging in modifications to your phone.
Thread Rules
This thread is for the development and furtherance of kernel features. There are a handful of rules to this development forum with which you must comply or you'll likely get ignored:
This is not a general Q&A thread, it is a development thread. Please use the Q&A thread for general questions.
Do not ask @UpInTheAir for support, this port is not one he maintains;
Do not post anything without first searching the forums, if your issue has been discussed before, you will get no response;
Do post anything relevant to the development and furtherance of the kernel. Please use the Q&A forums for questions and general discussions.
Features
Based on the latest available official Samsung source: Samsung OSRC
Base sources upgraded to Linux 3.10.108
A ridiculous number of optimizations and kernel bug reparations see all commits here;
Extensive Synapse app support for many kernel configurations;
ktoonservative Hotplugging CPU Governor (default, others available);
ktoonservative tweaks (e.g., overrides standard cpufreq screen-off handling);
Over/Under Clock and Voltages;
Wakelock control;
Multipath TCP Support (use Synapse to enable and select desired congestion algorithm);
F2FS support built in to kernel;
exFAT (OTG works), CIFS, NTFS, CIFS as modules (use Synapse to enable);
Permit FULL (auto)ROOT: ramdisk patched to support SYSTEM-LESS SuperSU or MAGISK;
Tether / Hotspot Fix Built In (N Kernels)
Auto-Install busybox & Sqlite3 to /system/xbin (on flash);
ramdisk base: per Sprint ROM releases;
KNOX WARRANTY VOID: 1;
SELinux PERMISSIVE (default) or ENFORCING (optional);
OTG support
DEEP SLEEP FIX;
init.d script support (place scripts in /system/etc/init.d & set permissions to 755 or 777 and reboot);
stock dt.img;
Mali GPU DVFS disabled for min/max frequencies;
Secure storage = false (prevent WIFI settings & passwords wiping on reboots);
Many descriptions are in the Synapse Application. If you require more info, follow the thread rules above.
Flash Descriptions:
Note that there are two downloads: an Update and Full boot image.
The Updates are for currently running ROMs. If you just want to update the kernel and related utilities (startup scripts, busybox) and have no other modifications to your boot image, download and install the Update version. The Update injects the kernel update into your existing boot image, it does not touch the remainder of the boot image. The update is also useful in cases when folks dirty flash ROMs just to change features or have older ROMs and want to try the latest kernel, therefore do not have the ROM flash install the kernel at all. The issue with that is the ROM flashes generally do not know to keep the kernel modules, so those get deleted. This updater will reinstall those as well. In brief, it is an update of the kernel and its important files only, it does not root the ROM as does the full version.
The Full boot image flash is a complete boot image, which is the normal flash. However, some ROMs install other systems (e.g., my hotspot fixes) which also modify the boot image, specifically files in the ramdisk. For initial, or clean installs of this kernel, download and install the Full flash. It will also root the ROM for you if not already rooted (SuperSU is installed). You will want to add other boot image modifying flashes after that (though there are not that many flashes that actually modify the boot image).
The general rule is this: if you are installing this kernel on a ROM and have never installed this kernel, use the full version. If you are already running tdhite SkyHigh on a ROM, download and flash the Update version of the kernel.
tdhite SkyHigh v7.30, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: a0b362bf71767cc4418d800ded163850
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.9.20180424. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.9.20180424:
Magisk Module AFH Mirror
MD5: b4f841be0f5881e0fbbd97152c714e0d
Memory leak fixes (no known/reported leaks remain).
Updated embedded Magisk to v18.00 and roots the phone therewith.
Passes SafetyNet Checks!
Recovery Flashables for based on latest MM kernel sources and firmware (PL3 through QB1) ROMS
Dramatic boot up time improvements (impressively fast)..
Ramdisk (boot image) will work with PL3 through QB1 Firmware.
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . . subsequent boots are smoking fast.
Kernel Update (updates only the kernel in your existing boot image and utils)
XDA Downloads: tdhite SkyHigh v4.10 on XDA
AFH Mirror: tdhite SkyHigh v4.10 Update Only;
MD5 Hash: 23ebe23c2c1a326f9b9970a2c1746457
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v4.10 Full;
MD5 Hash: 60982a190838f7cb5dedd749821bc93e
Instructions
Make sure you are running a MM 6.0.1 or N 7.0 (Stock is fine);
Make sure you have TWRP 3.0.1-0 (or higher version) loaded as your customer recovery;
Download the TWRP flashable zip for your specific version of Android and firmware, placing the flash on your phone for subsequent 'Install' in TWRP;
Reboot into TWRP Recovery;
The smart user will perform a backup in TWRP;
Flash the zip'
Reboot System;
Use the Synapse App to configure the many options as you deem desirable, of course pursuant to the DISCLAIMER.
The first boot will take a while, give it some time. A couple minutes is not unlikely at all, possibly more.
Credits
@UpInTheAir - early, initial base Synapse support and kernel optimizations
@topjohnwu - root & Magisk app
@Chainfire - root & SuperSU app
@AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
@halaszk88 - patches and some Synapse code @UpInTheAir adapted to many of his kernels
@dorimanx - BusyBox and various ramdisk tweaks/ideas
@apb_axel - @UpInTheAir and @tdhite (for this port) adapted and used many of the Synapse controls
@arter97 - various source fixes/patches
@ktoonsez - ktoonservative hotplug governor
XDA
Samsung OSRC
and many others!
check gitHub source credits
Users that provide proper bug reports with an element of self-troubleshooting. Constructive feedback is always welcome.
IF ANYONE WAS FORGOTTEN, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
Older Versions are in Post #3 below.
As a final note, the sources are pulled by a Google repo manifest, which is within the "teamspr" project in link listed in the 'Source Link' below. The manifest shows the various github repositories for the project. If you need help with repo, let me know and we will get you setup with the code and how to view it.
XDA:DevDB Information
SM-G920P SkyHigh Kernel Port, Kernel for the Sprint Samsung Galaxy S6
Contributors
tdhite, @UpInTheAir (for initial base)
Source Code: https://github.com/TeamSPR
Kernel Special Features: Synapse ++ | EXT4 | F2FS | exFAT | NTFS | CIFS | Linux 3.10.108 | many optimizations and bug reparations | ktoonservative hotplugging governor | Optional SElinux permissive | Deep sleep fix | init.d support | See above for more.
Version Information
Status: Stable
Current Stable Version: 7.30 (v1.8.20190119)
Stable Release Date: 2019-01-19
Created 2016-04-02
Last Updated 2019-01-21
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use the software, or convey it to someone else, you and all subsequent conveyees are bound by the following:
LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
Assumption of the Risk of Use
YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY, IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR, CORRECTION OR OTHERWISE.
Disclaimer of Title Warranty
THERE IS NO WARRANTY OF TITLE FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING ANY CONVEYOR OF THE PROGRAM MAKES NO WARRANTY OF ANY KIND THAT HE OR SHE HAS ANY TITLE OR THE RIGHT TO TRANSFER ANY TITLE TO THE PROGRAM TO YOU. YOU ACCEPT THAT, IN FACT, YOU RECEIVE NO TITLE TO ANY OF THE PROGRAM.
Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Reserved
Older Versions
tdhite SkyHigh v7.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 71996970885feb2cddf6cfa101891793
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.9.20180424. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.9.20180424:
Magisk Module AFH Mirror
MD5: b4f841be0f5881e0fbbd97152c714e0d
Added SmartAssV2 Governor.
Nexus governor should now be visible (but is very unstable, do not use this for now).
Updated embedded Magisk to v16.40 and roots the phone therewith.
Passes SafetyNet Checks!
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
tdhite SkyHigh v7.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
XDA Project Mirror
MD5 Hash: 8d02f4698df1a7ed54673209b9aae01a
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.8.20180424. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.7.20180101:
Magisk Module AFH Mirror
MD5: e533e7b90202beba93df462bc945f9c8
Rebased all commits onto latest Samsung released kernel sources.
Updated embedded Magisk to v16.30 and roots the phone therewith.
Passes SafetyNet Checks!
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
The sky-high module now supports calling a script every time the cortex tuning script executes (appx. every five seconds). Just place a valid script in "/sdcard/SkyHigh/scripts/user.sh" and that will get called by the /system/xbin/cortexbrain-tune.sh script each time it executes in the background. Be very careful, the user.sh script has full root access!
tdhite SkyHigh v6.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 6126ec42eea993398a08a205d514e5e2
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.7.20180101. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.7.20180101:
Magisk Module AFH Mirror
MD5: e533e7b90202beba93df462bc945f9c8
Updated embedded Magisk to v15.10 and roots the phone therewith.
Passes SafetyNet Checks!
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
tdhite SkyHigh v6.00, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 646af6e2cbe63224d116595e1eec3597
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.6.20171210. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.6.20171210:
Magisk Module AFH Mirror
MD5: 91a0eb89329f25bab6aab6f656b04745
Updated to Linux v3.10.108.
Additional optimizations and security additions.
Passes SafetyNet Checks!
Roots the phone with Magisk v14.5(1456).
Set the Magisk "Update Channel" to Beta until the official release finally arrives.
Remember that when you try to update the MagiskManager app manually, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
tdhite SkyHigh v5.02 Nougat, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
Kernel:
Kernel AFH Mirror
MD5 Hash: 8d049afab573d9e20ab65c1c73a6af31
Note: The kernel flash installs the Magisk Module: magisk-module-skyhigh-v1.50.201709729. If a later module exists below, flash that after flashing the kernel. There is no need to refresh the kernel just to update the modules.
SkyHigh Magisk Module v1.5.20170929:
Magisk Module AFH Mirror
MD5 Hash:e3f90a6e80c239add1803a78911018be
Passes SafetyNet Checks!
Roots the phone with Magisk v14.2 (MagiskManager will request that you update as appropriate)
Remember that when you try to update the MagiskManager app manually, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
Kernels for Nougat 7.0:
tdhite SkyHigh v5.01 Nougat, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
AFH Mirror
XDA Downloads
MD5 Hash: 0e3eb7b60276c4ce05049b517a23fd7c
Passes SafetyNet Checks!
Many new optimizations (even more than beta 4.99b).
Roots the phone with Magisk v12.0
Places the MagiskManager 4.3.3 in /sdcard/MagiskManager-4.3.3.apk for easy installation after flashing the kernel. Just open your file browser and click on the file, then select install.
If you are SuperSU or Magisk v13 rooted, you should uninstall your root manager app and unroot. The kernel flash will re-root you. If you are Magisk v12.0 rooted, no work needed, just flash the kernel and profit!
Both Magisk and SuperSU provide for uninstall applications. If you don't know how to do that, read the SuperSU or Magisk pages. It is not difficult -- basically for SuperSU, you need to: 1) delete the SuperSU app while in Android ROM; 2) boot into TWRP (recovery); 3) delete /data/su.img and /data/stock_boot_*.img; and finally 3) flash this kernel, but not before). For Mgisk, just use the Uninstaller module.
Note, you need to update the MagiskManager app after booting up. The app, as installed by the Magisk installer, will tell you to update from the App store -- your phone is rooted, you just need to update the app. The app installer (apk) is placed by this kernel flash in /sdcard/MagiskManager-4.3.3.apk for easy access (see above).
Remember that when you try to install the manager app, using your file manager, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
After you install the Magisk Manager, Synapse will obviously request root access, grant it 'forever' so it will work on boot thereafter. On first time running, Synapse might (rarely) fail and quit or complain there is no root or uci access. To fix that, just open your 'Recents' list and swipe away Synapse. Restart it and it should now have root and work properly. Setup the kernel as you like from there.
The kernel startup scripts are now part of a Magisk module. If you reinstall Magisk by your self, it may clobber that module. I'll post the zip for that if folks have trouble. DO NOT DELETE THE SKYHIGH MODULE in the MagiskManager app.
tdhite SkyHigh v5.00 Nougat, Magisk Rooted, Recovery Flashable for N (Nougat) ROMS
AFH Mirror
XDA Downloads
MD5 Hash: b28ea6ad870ba849ba442b96700348a1
Many new optimizations (even more than beta 4.99b).
Roots the phone with Magisk v12.0
Places the MagiskManager 4.3.3 in /sdcard/MagiskManager-4.3.3.apk for easy installation after flashing the kernel. Just open your file browser and click on the file, then select install.
If you are SuperSU or Magisk v13 rooted, you should uninstall your root manager app and unroot. The kernel flash will re-root you. If you are Magisk v12.0 rooted, no work needed, just flash the kernel and profit!
Both Magisk and SuperSU provide for uninstall applications. If you don't know how to do that, read the SuperSU or Magisk pages. It is not difficult -- basically for SuperSU, you need to: 1) delete the SuperSU app while in Android ROM; 2) boot into TWRP (recovery); 3) delete /data/su.img and /data/stock_boot_*.img; and finally 3) flash this kernel, but not before). For Mgisk, just use the Uninstaller module.
Note, you need to update the MagiskManager app after booting up. The app, as installed by the Magisk installer, will tell you to update from the App store -- your phone is rooted, you just need to update the app. The app installer (apk) is placed by this kernel flash in /sdcard/MagiskManager-4.3.3.apk for easy access (see above).
Remember that when you try to install the manager app, using your file manager, be sure you have "Unknown Sources" checked on in Settings -> Lock Screen And Security.
After you install the Magisk Manager, Synapse will obviously request root access, grant it 'forever' so it will work on boot thereafter. On first time running, Synapse might (rarely) fail and quit or complain there is no root access. To fix that, just open your 'Recents' list and swipe away Synapse. Restart it and it should now have root and work properly. Setup the kernel as you like from there.
The kernel startup scripts are now part of a Magisk module. If you reinstall Magisk by your self, it may clobber that module. I'll post the zip for that if folks have trouble. DO NOT DELETE THE SKYHIGH MODULE in the MagiskManager app.
Kernels for Marshmallow 6.0.1:
Recovery Flashables for based on latest kernel sources and firmware (CPL3 and QA2) ROMS
Ramdisk (boot image) updated to QA2 (though will work on CPL3 as well).
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image and utils)
AFH Mirror: tdhite SkyHigh v3.70 Update Only;
MD5 Hash: c6432dbcb67a15f0663c11c5132eb0d1
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v3.70 Full;
MD5 Hash: 0e8f7450cf9b01d4173b64cd50afc55c
Recovery Flashables for based on latest kernel sources and firmware (CPL3) ROMS
Ramdisk (boot image) updated to CPL3 (there are many security context changes)
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image and utils)
AFH Mirror: tdhite SkyHigh v3.60 Update Only;
MD5 Hash: 1e98841a76aea39146cd27b478c2e5bc
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v3.60 Full;
MD5 Hash: 153506f01cb2355b54d70c467a10ebff
Recovery Flashables for based on latest kernel sources and firmware (CPJ1 and CPK1) ROMS
Ktoonservative governor defaults to allow additional screen-off CPUs
Reduced polling for cpufreq info when screen is on
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image and utils)
AFH Mirror: tdhite SkyHigh v3.50 Update Only;
MD5 Hash: a4c68f1a7e03da40795d8abd56586f4e
Kernel Full Boot Image (installs entire boot image and utils)
AFH Mirror: tdhite SkyHigh v3.50 Full;
MD5 Hash: b1c590f644a4023f3bf53ff330c38c80
CPJ1 and CPK1 base
Ktoonservative governor now overrides default screen-off clock speed handling
Fixed shell access for crond (crontabs will now work properly)
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Kernel Update (updates only the kernel in your existing boot image)
AFH Mirror: tdhite SkyHigh v3.40 Update Only;
MD5 Hash: 528f0e317c93bd7d645b16b47727e56f
Kernel Full Boot Image (installs entire boot image)
AFH Mirror: tdhite SkyHigh v3.40 Update Only;
MD5 Hash: c4c811233f016ab555adf06c86739721
CPJ1 and CPK1 base
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.36a;
MD5 Hash: 6cea4a864da3991142f899525e1375d2
Changes:
Rebuilt specifically to fix the kernel modules (they were not loading in previous PJ1 builds when enabled in Synapse).
No need to wipe any partitions, just flash and reboot.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Previous Downloads for Latest (PJ1) ROMS
PJ1 Previous Versions Download links removed due to bad module builds.
Ramdisk based on (PJ1) Stock ROM.
Cron service repairs (many).
ADB support fixed, now uses standard (secure) access from Stock ramdisk.
SuperSU: @Chainfire v2.78-SR1
Download for PI3 ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.34;
MD5 Hash: 2253a78d5d5ae4413d63ebf424f3034d
Changes:
Ramdisk based on G910PVPS4CPI3 (PI3) Stock ROM.
SuperSU updated to: @Chainfire v2.78-SR1
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Download for PF4 Based ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.3;
MD5 Hash: 47eb72636cf66e9a6c720b8ab141027d
Changes:
Ramdisk based on PF4 Stock ROM.
Busybox installation reparations for Stock ROMs.
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Download for PD3 Based ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.22;
MD5 Hash: 8d6b47c2b9c73b8f23b26a893880154f
Note: This is likely the last update for PD3 and below ROM bases. PF4 and above will get further updates.
Changes:
Busybox installation reparations for Stock ROMs.
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
Download for PD3 and Earlier Based MM ROMS
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.21;
MD5 Hash: 8c3deedc7d1acb2ee19657dc6ecff00e
Changes:
SuperSU updated to 2.76
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v3.2;
MD5 Hash: 1d9ac4781019de75e33ac5b86259dc4e
Changes:
F2FS Support updates and backports from upstream (kernel.org) kernel (built-in)
Multi-path TCP support with matching TCP congestion algos
Many minor optimizations and bug fixes from upstream -- see sources for further details.
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.84;
MD5 Hash: 57dc34e5b2f6142255b0e003f94290b2
Changes:
F2FS Support (built-in)
exFAT Support as module (use Synapse to enable); works with OTG
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.83;
MD5 Hash: 9c0cf7d66b362e7a54b6b9872a935e8b
Changes:
SuperSU 2.71 updated
Boot time optimizations
Busybox install support
Incorporates all prior updates as well.
NOTE: First boot after flash will take a bit and may reboot for SuperSU updating. Let it breathe . . .
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.82;
MD5 Hash: 08f14d05999aa23a75a4aace5ce1e18b
Changes:
Flash installer fixes broken ROMs (mistaken selinux contexts on telephony services);
Incorporates all prior updates as well.
TWRP Flashable:
AFH Mirror: tdhite SkyHigh v2.81;
MD5 Hash: 0bb4ddaed59c188b084dc498a1fb1db7
Changes:
Fixed Synapse display errors (all known);
Sensor wakelock support (required to fix Synapse display error)
NOTE: THIS IS A BETA VERSION AND SUBSEQUENT VERSIONS PRIOR TO RELEASE WILL NOT BE CHANGE LOGGED;
AFH Mirror: tdhite SkyHigh v2.8;
MD5 Hash: d93fa401ee23f3b689edaa0614cedefa
may i ask about the battery life of this kernel?
is there any known issue list that i should read before flashing this?
thank you very much for this first kernel for our G920P.
tdhite said:
Port of the SkyHigh Kernel, originally created by @UpInTheAir, to SM-G920P (Sprint Galaxy S6).
This port is rebase of the SkyHigh kernel commits onto the G920P kernel base sources, as well as other and modifications relevant to Sprint Galaxy S6 device. The boot image build is not embedded in the kernel sources, as it is in the original, rather is an automated build in a separate project.
DISCLAIMER
Always READ THE DISCLAIMER before engaging in modifications to your phone.
NOTE: This Thread is Under Construction and will be Completed by End of Evening, 04/03/2016, not before. Please honor good 'dev thread' etiquette and do not post anything until you 1) have the kernel; 2) have installed it; and 3) have a problem or feature request related to it.
This is a healthy effort to both create the port and build the content in this thread so give fair time as we all have important life duties outside XDA. Also, this is not a general Q&A thread. That is why we have multiple forums, please use the Q&A thread for general questions. That forum will autogenerate soon enough.
Thread Rules
This thread is for the development and furtherance of kernel features. There are three rules to this development forum with you must comply:
Do not ask @UpInTheAir for support, this port is not one he maintains;
Do not post anything without first searching the forums, if your issue has been discussed before, you will get no response;
Do post anything relevant to the development and furtherance of the kernel. Please use the Q&A forums for questions and general discussions.
Features
A ridiculous number of optimizations and kernel bug reparations see all commits here;
ktoonservative Hotplugging CPU Governor (default, others available);
Permit FULL ROOT: ramdisk patched to support SYSTEM-LESS SuperSU v2.70 (RC);
Based on official Samsung source: Samsung OSRC;
ramdisk base: G920PVPU3CPB6;
KNOX WARRANTY VOID: 1;
SELinux PERMISSIVE (default) or ENFORCING (optional);
DEEP SLEEP FIX;
Auto-Install busybox v1.24.1-Dorimanx & Sqlite3 to /system/xbin (on flash);
Linux 3.10.101;
init.d script support (place scripts in /system/etc/init.d & set permissions to 755 or 777 and reboot);
adb insecure;
stock dt.img;
Mali GPU DVFS disabled for min/max frequencies;
Secure storage = false (should prevent WIFI settings & passwords wiping on reboots);
Synapse app support for many kernel configurations;
Many descriptions are in the Synapse Application. If you require more info, follow the three rules above.
Synapse Feature Support
Many! -- details coming soon . . .
Download
TWRP Flashable:
NOTE: THIS IS A BETA VERSION AND SUBSEQUENT VERSIONS PRIOR TO RELEASE WILL NOT BE CHANGE LOGGED;
AFH Mirror: tdhite-G920P-SkyHigh-16-04-02.zip;
MD5 Hash: 3209035090a6c207596321e91882b4ca
Instructions
1) Make sure you are running a MM 6.0.1 ROM (Stock is fine);
2) Make sure you have TWRP 3.0.1-0 (or higher version) loaded as your customer recovery;
3) Download the TWRP flashable zip and place on your phone for subsequent 'Install' in TWRP;
4) Reboot into TWRP Recovery;
5) Flash the zip
6) Reboot System
The first boot will take a while, give it some time. A couple minutes is not unlikely at all, possibly more.
Credits
@UpInTheAir (and his family :angel
@Chainfire - root & SuperSU app
@AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
@halaszk88 - patches and some Synapse code @UpInTheAir adapted to many of his kernels
@dorimanx - BusyBox and various ramdisk tweaks/ideas
@apb_axel - @UpInTheAir and @tdhite (for this port) adapted and used many of the Synapse controls
@arter97 - various source fixes/patches
@ktoonsez - ktoonservative hotplug governor
XDA
Samsung OSRC
and many others!
check gitHub source credits
Users that provide proper bug reports with an element of self-troubleshooting. Constructive feedback is always welcome.
IF ANYONE WAS FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SM-G920P SkyHigh Kernel Port, Kernel for the Sprint Samsung Galaxy S6
Contributors
tdhite, tvm2487, @UpInTheAir (for many of the commits picked into this kernel).
Source Code: https://github.com/teamspr/kernel/tree/skyhigh
Kernel Special Features: Synapse ++ | EXT4 | exFAT | NTFS | CIFS | Linux 3.10.101 | many optimizations and bug reparations | ktoonservative hotplugging governor | Optional SElinux permissive | Deep sleep fix | init.d support | See above for more.
Version Information
Status: Beta
Current Stable Version: v2.8
Stable Release Date: 2016-04-02
Current Beta Version: v2.8
Beta Release Date: 2016-04-02
Created 2016-04-02
Last Updated 2016-04-02
Click to expand...
Click to collapse
Excellent job Tom! You worked extremely hard on this and it paid off sir.
Sent from my SM-G925P using XDA-Developers mobile app
If i flash this kernel,can i have mobile hotspot menu?
mahdi72 said:
If i flash this kernel,can i have mobile hotspot menu?
Click to expand...
Click to collapse
Please use the q&a thread for questions, as stated in the OP, in the future. That said, a kernel has nothing to do with menus.
Sent from my SM-G920P using Tapatalk
I flashed this on my S6 and man I sure miss getting to use this kernel and synapse on my Sprint Note 5 but at @UpInTheAir is taking some time off till the end of April until he updates it to work on 6.0.1. I have a couple of java string errors when it comes to the wakelock controls but that might be due to the issue I'm having with the stock ROM. For some reason after I ODINed the 6.0.1 firmware on my phone won't activate and it says it is on Samsung Network but hotspot and everything else works so I wasn't going to mess with it. Great job with the kernel. I cannot wait till my note has it again.
Sent from my SM-N920P using XDA-Developers mobile app
Here are the screenshots of what it says. I know you probably need a logcat but I'm pretty sure I know what the problem is.
{
"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"
}
Sent from my SM-G920P using XDA-Developers mobile app
Love this kernel as it doesn't give you that warning "kernel not seandroid enforcing" but I still benchmark slower than stock even with everything set to performance. I don't understand!
Any feedback would be greatly appreciated! Thank you!
Eric
For some reason my phone won't boot up with this kernel :/
my S6 didnt bootup after flashing TWRP 3.0.1-0 actually
i had to use the old TWRP 3.0.0-1 and flashed this kernel after, and it works.
Bobthahog said:
Here are the screenshots of what it says. I know you probably need a logcat but I'm pretty sure I know what the problem is. View attachment 3707387View attachment 3707388
Sent from my SM-G920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Ugh. I know the issue. Will rev a fix. Not sure how i missed that, but adding tests to cover this issue as well.
Sent from my SM-G920P using Tapatalk
tdhite said:
Ugh. I know the issue. Will rev a fix. Not sure how i missed that, but adding tests to cover this issue as well.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Thanks man. U did a magnificent job porting this over to the S6. I just figured it was the issue I was having with phone not wanting to activate on Sprint network.
Sent from my SM-N920P using XDA-Developers mobile app
Updated -- 04/09/2016
The flash, kernel and synapse support was updated to fix reported errors.
See the OP for download and flash instructions (no different instructions, they are just in their normal place).
tdhite said:
The flash, kernel and synapse support was updated to fix reported errors.
See the OP for download and flash instructions (no different instructions, they are just in their normal place).
Click to expand...
Click to collapse
Phone still won't boot up! -__- but now it gets stuck at the "Sprint LTE Plus" splash screen (instead of the Samsung splash screen).
I honestly don't know how to help you. I've asked for logs, rom info yet get nothing. How long did you wait for boot? OP says can take a while. You cannot send a logcat?
Seriously, I'd love to help, but it takes more info when one phone out of many, many others that work fine has an issue. There is clearly something about your rom or apps or whatever, but I have nothing to go on to help you.
Sent from my SM-G920P using Tapatalk
I flashed the updated kernel and it's working great. No errors in synapse. Awesome job.
Sent from my SM-G920P using XDA-Developers mobile app
---------- Post added at 05:12 AM ---------- Previous post was at 05:11 AM ----------
I flashed the updated kernel and it is working great. No errors in synapse. Awesome job man.
Sent from my SM-G920P using XDA-Developers mobile app
tdhite said:
I honestly don't know how to help you. I've asked for logs, rom info yet get nothing. How long did you wait for boot? OP says can take a while. You cannot send a logcat?
Seriously, I'd love to help, but it takes more info when one phone out of many, many others that work fine has an issue. There is clearly something about your rom or apps or whatever, but I have nothing to go on to help you.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
OK so I feel like an idiot bro... I didn't know that your kernel script wiped cache/dalvik cache lmao -__-
THAT'S why it was taking so long to boot. Sorry bro! -__- Anyways this thing is smooth as hell!
Nevermind... Had to uninstall this kernel. My phone kept turning off & rebooting itself. No problems what-so-ever with the stock kernel. This kernel was causing some major hiccups with my phone.
This rom is tested and working on SM-G930F/FD/K/L/S/W8 variant only! Do not try this on other variants without any backup!
{
"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"
}
Why I did another rom for you on XDA? Many people asked me to do a basic version with some nice adaption because they actually really like stock. So along with my SuperStock Kernel I decided to make the SuperStock-Rom for a very stock near feeling. It features Odex apps and framework for max battery and performance! If you want something more customizable I recommend you to go for SuperMan-Rom and if you really like the grace UX features of the N7 there is also my HydraRom. I hope one of this roms fits your needs!
Rom Features:
V1.2 Marhsmallow:
- BPLB base
- Latest BPLB kernel, superstock kernel or superkernel
- November security patch
- SuperSU V2.79, Phh superuser r275 or magisk phh r266-2
- Magisk v9
- Xposed v86.2 or v87.1
- Stock emojis, ios emojis or android n emojis
- Rom is full ODEX for better speed
- Fixed googles overlay issue
- Gear VR working
- OTA support
- Sound mod included in aroma
- Aroma installer
- Debloat menu in aroma
- sd card rw
- system mounted as rw
- dm-verity disabled
- init.d support
- wakelock fix for google services
- csc features included
- Applock supported
- Advanced wifi settings
- private mode working (with permissive kernel)
V2.11.0 Nougat:
- DQJ1 base Nougat
- Latest DQJ1 kernels
- October security patch
- SuperSU V2.82 SR5, Phh superuser or MagiskSU
- Magisk v14.3
- Rom is full ODEX for better speed
- Fixed googles overlay issue
- Gear VR working
- Aroma installer
- Debloat menu in aroma
- sd card ro
- system mounted as rw
- dm-verity disabled
- init.d support
- csc features included
- Advanced wifi settings
- Auto model choose in script to flash right files
- Auto update BL/CP for F/FD model in you choose in aroma
- iOS emojis
- Sound Mod V19
Bugs:
- You tell me
Rom review by @shark jungle:
HOW-TO Install the rom:
0. Make sure you have ticked OEM Unlock in Developer settings!
1. Download latest bootloader and modem from here:
Bootloader/Modem
2. Download latest odin
3. Flash BL in BL tab and CP in CP tab of odin. Then follow the steps on this side until you get a working custom recovery: TWRP
4. If you are done with bootloader, modem and recovery we can move on, boot into twrp holding power, home button and volume up while phone is powered off
5. This will delete all your personal data! Click on wipe, format data and type "yes"
6. Wait until it is finished then click reboot, reboot to recovery
7. Now connect your phone to PC and copy the rom file inside your internal or external sd card
8. Flash the rom and wait until it is finished
9. Reboot your phone and enjoy !
Downloads:
V2.11.0 available on AndroidFileHost
Thread on Grifo Development
V1.2 on Androidfilehost (latest MM version)
SM-G930F/FD Modem and Bootloader
SM-G930W8 Modem and Bootloader
CSC Selection V2.3.5
Telegram:
If you wish to ask me some questions, join my telegram chat about SuperStock-Rom. You can also join if you just want to have a quick chat with me anyway just click on this link: Telegram invite link
Saying thanks:
If you enjoy and appreciate my work, I would be very pleased if you hit thanks on this post here, then I'm a very happy guy! If you say you want to do more about it, you can donate me with paypal using this link:
PayPal
I already say thanks to all of you! :highfive:
Credits:
- SuperR for his great unpack kitchen
- of course samsung for their firmware and source
- topjohnwu for his magisk and xposed systemless
- rovo for xposed
- chainfire for his root
- topjohn for xposed
- phh for superuser
- amarullz for aroma installer
- and last but not least the great XDA community for making me better and greater each day!
XDA:DevDB Information
SuperStock-Rom for herolte, ROM for the Samsung Galaxy S7
Contributors
Tkkg1994
Source Code: https://gitlab.com/Tkkg1994/SuperStock-Rom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Custom Recovery
Based On: Stock Based
Version Information
Status: Stable
Current Stable Version: V2.11.0
Stable Release Date: 2017-10-27
Created 2016-11-08
Last Updated 2017-10-27
Changelog
Changelog for MM versions (1.X):
SuperStock-Rom V1.0:
- Initial release!
SuperStock-Rom V1.1:
- Rebased on BPJG release
- November security patch
- Kernels updated with BPJE source drop and BPJG ramdisk
- Magisk phh updated to r266
- Phh updated to r266
SuperStock-Rom V1.2:
- Rebased on latest BPLB release
- December security patch
- Updated magisk to V9
- Updated Magisk apk to V2.5
- Updated busybox to V1.25
- Updated busybox app
- Updated SuperSU to V2.79
- Updated phh superuser to r275
- Updated phh apk to latest beta 10 material
- Updated phh magisk to r266-2
- Updated Xposed to 87.1 version
- Updated Xposed app
- Updated host files
- Added ablocker app as user app
- Added Aroma choice about default adblocker enabled/disabled
- Updated StockKernel to BPLB
- CSC updated to XEF BPL2
- SuperKernel updated to 1.9.6
- SuperStock updated to 1.6
Changelog for Nougat versions (2.X):
SuperStock-Rom V2.0 Beta:
- Based on latest G935FXXU1ZPKK base
- Android Nougat 7.0 update!
- november security patch
- Full nougat stock kernels included
- magisk updated to V9
- phh magisk updated to r266-2
- supersu updated to SR4 helios (all credits to @lyapota)
- removed csc selection as there is only 1 csc for now
- updated adblocker app
- csc features included as on V1.1
- kept ODEX as previous V1.1 version
- Busybox updated with a new app
- Many new things due to android N in general
- I must remove some debloat option as aroma only supports zips till 2 GB
- Model is kept G935F so you can enjoy all edge panels and edge features!
- of course no force encryption
- multi user support
- modem will be auto updated during rom flash! (If you have a F/FD model)
SuperStock-Rom V2.1 Beta:
- Rebased on latest ZPL3 base
- December security patches
- SuperSU update to SR5
- Added option to enable or disable adaway in aroma
- Updated adaway hostfile
- Updated all kernels to ZPL3 base
- Updated the included modems
- Private mode now working fine
- Some more bloatware removed
SuperStock-Rom V2.2 Beta:
- Fully rebased to latest ZPLH release
- Both edge and flat kernel updated to ZPLH base
- Updated modem to ZPHL release
- New: included auto update bootloader on F/FD models as well to ZPLH release
- CSC updated to ZPLH release
- SuperSU updated to V2.79
- Samsung Music app updated
- Phh superuser apk updated
- adblocker hostfile updated
- No more version choose in aroma, everything will be flashed automatically (depending on which s7 version you got)
SuperStock-Rom V2.3 Beta:
- Rebased on latest ZPLN release
- Updated CSC to ZPLN
- Updated kernels to ZPLN
- Updated Modems to ZPLN
- Updated SuperSU to official SR1 update (should fix all issues we had with supersu before)
SuperStock-Rom V2.4:
- Now based on latest official DPLT release!
- Stock kernel updated to official DPLT
- CSC updated to DPLT
- Bootloader updated to DPLT (and now selectable in aroma as well)
- Modem updated to DPLT (also selectable via aroma)
- CSC countries are selectable (those available in BTU csc)
- SuperStock-Kernel V2.0 included
- SuperKernel V2.0 included (busybox needs to be at /sbin for synapse!)
- init.d tweaks added
- build.prop tweaks added
- Recovery is now included and can be updated via aroma
- ios emoji added
- Sound mod added (needs testing)
- Viper4android added, magisk viper4android as well
- ARISE sound mod added
- Magisk updated to V10.2 (if you choose stock kernel it will flash V9, otherwise it won't boot)
- Magisk app updated
- Phh magisk updated to R2
- Phh app updated
- host file updated
- SuperSU updated to V2.79 SR3
- Busybox updated to 1.26.2 (with magisk support now!)
- Secret tab working in sbrowser (credits @mwilky)
- Private mode working fine on both kernel
- Aroma is most likely same as SuperMan (no more model choose, all handled in scripts)
- Backup/restore of aroma selections added
- AppLock added for N (csc feature) credits to @Repulsa
- All variants have now the proper model number (SM-G930F/K/L/S/W8 etc)
- Some other things I may forgot
SuperStock-Rom V2.5:
- Rebased on DQB7
- February security patch
- Updated included BL to DQB7 and modem to DQB1
- BTU multi csc included (DQB3 version)
- Updated all kernels with ramdisk to DQB7
- Magisk updated to V11.1 (no need for superuser apk anymore)
- Updated MagiskManager to V4.1
- Busybox updated
- Adblocker updated
- Sound mod updated to V19
- Camera mod added (V8.1)
- Arise sound mod removed (they got their own aroma installer now)
- All previous features included
SuperStock-Rom V2.6:
- Based on DQCG
- March Security patch
- Magisk Manager updated
- Bootloader/Modem updated to DQCG
- W8 Bootloader/Modem added
- Additional fonts added in aroma
- Knox added to choose in aroma
- New build.prop tweaks added
- CSC updated
- All kernels updated to 2.4.2 version
- Magisk updated to V11.6
- Many bloat apps added to choose from (like on SuperMan)
- Aroma updated to latest mods (like Superman)
SuperStock-Rom V2.7:
- Based on latest DQD2 firmware
- April security patch
- BL/CP both updated to DQD2
- SuperKernel/SuperStock-Kernel and stock kernel updated to DQD2
- Magisk updated to V12
- Phh root updated to r310
- Magisk Manager updated
- All extra apps (such as snapchat, telegram etc) updated
SuperStock-Rom V2.8:
- Rebased on DQEF base
- includes latest bootloader and modem in aroma
- updated included TWRP to 3.1.1
- updated kernels to v2.6 (with new linux and source)
- May security patch
- OTA is now choosable in aroma too
SuperStock-Rom V2.9.0:
- Updated base of the rom to most recent DQFM
- Updated all kernels to DQFM including ramdisk and latest kernels from earlier today
- Updated Magisk to V13.1
- Updated SuperSU to 2.82 SR1
- Updated included BL/CP of F/FD/W8 to most recent versions
- Includes June security patch
SuperStock-Rom V2.10.0:
- Updated base to DQHY
- Updated all included kernels to latest DQH8 base
- Updated Magisk to V14.0
- Updated SuperSU to 2.82 SR3
- Updated included BL/CP of F/FD/W8
- Includes August security patch
- Updated Samsung Fonts app
- Removed OTA update, this wasn't working anymore
- Removed viper4android due to problems with sound, please use ARISE or similar mods
- Updated busybox to most recent v1.27.2 version
- Added a new busybox to the selection
- Added some more apps into debloat options
SuperStock-Rom V2.11.0 FINAL:
- Updated to latest DQJ1 base
- Includes latest October security patch
- Fixes blueborne
- Updated all kernels to DQJ1
- Updated SuperSU to SR5
- Updated Magisk to latest V14.3
- Added Magisk Xposed V88.1 into aroma selection
- Added Oreo emojis into aroma selection
- Updated modded camera
- Updated included bootloader/modems
- Updated the adblocker host file
- Updated modded fonts app
- Fake system state to official
Useful posts and links
Odin:
Find all latest odin and samsung tools on this link: Samsung-Tools
In case you need help:
Try to take a look at my Q&A Thread where hopefully some general questions are already answered.
TWRP links:
TWRP S7 Thread
Official TWRP website for s7
Bootloader and Modems:
SM-G930F/FD BL and CP
SM-G930K BL and CP
SM-G930L BL and CP
SM-G930S BL and CP
SM-G930W8 BL and CP
Xposed Threads:
Wanam Xposed V87
Systemless Magisk Xposed V86.6
Official Xposed V87 (DOES NOT WORK ON SAMSUNG DEVICES) visit this website only for changelogs and infos from rovo!
Material Xposed Installer
General Xposed Discussion
Magisk related Threads:
Magisk V9
Magisk Discussion
How-To create a Magisk module
PHH magiks superuser
Magisk module collection
Root related Threads:
Sound Mod V18
How to encrypt on custom rom
Phh's superuser
Phh's hidesu
Phh's official apk
Phh's material APK
Stable SuperSU releases
Beta SuperSU releases
Chainfires suhide
Kernels Threads:
Kali Nethunter
TGP Kernel
SuperStock Kernel
Prometheus Kernel
SuperKernel
Voltaqe kernel
Roms made by me:
SuperMan-Rom which you are currently on its thread
HydraRom which is a full note 7 rom compatible with our s7.
SuperStock-Rom which is as close to stock as possible with some nice additions. Android 7.0 Nougat Beta is available for it!
Samsung Links:
Sammobile Website
Latest samsung apks
Samsung Opensource Center
Live samsung updates
Fast firmware downloads
Good Lock:
Latest Good Lock APK can always be found on Apk Mirror.
Thread about CSC:
Download latest CSC from CSC Selection V1.9
All CSC's ever released
How to donate:
Donation via normal PayPal
Donate via PayPal.me
Best StockROM experience. Running smooth with superstock kernel. Best I tried so far!
Will try this the upcoming week.
Sounds very promissing ty as always
Thanks ! I will be test ! I love rom custom with stock, just little modification :3
abe2912 said:
Best StockROM experience. Running smooth with superstock kernel. Best I tried so far!
Click to expand...
Click to collapse
Thank you
roba93 said:
Will try this the upcoming week.
Sounds very promissing ty as always
Click to expand...
Click to collapse
No problem
Drice81 said:
Thanks ! I will be test ! I love rom custom with stock, just little modification :3
Click to expand...
Click to collapse
Yeah then this is exactly for you
This is super. Best battery life. Thanks
Inviato dal mio SM-G930F utilizzando Tapatalk
Security patch date?
Thanks a lot
Holy S.... Nice dude. I downloading and testing this thing. Big Thanks man. This is what i whant
PopaStefanx said:
This is super. Best battery life. Thanks
Inviato dal mio SM-G930F utilizzando Tapatalk
Click to expand...
Click to collapse
Nice and no problem!
amtomio2004 said:
Security patch date?
Thanks a lot
Click to expand...
Click to collapse
October
Jazz2000 said:
Holy S.... Nice dude. I downloading and testing this thing. Big Thanks man. This is what i whant
Click to expand...
Click to collapse
Enjoy!
Sent from my SuperMan powered SM-G930F
Installed,maybe it is space for more debloating
king118 said:
Installed,maybe it is space for more debloating
Click to expand...
Click to collapse
If you send me a list of additional removable apps without breaking any features I am waiting
Tkkg1994 said:
If you send me a list of additional removable apps without breaking any features I am waiting
Click to expand...
Click to collapse
Hmm Voice Wake/S voice ,Weather,Edge Panel(maybe a option to install or not in aroma).Now the question is how many people use the Gear Vr on S7 in order to remove or not.
king118 said:
Hmm Voice Wake/S voice ,Weather,Edge Panel(maybe a option to install or not in aroma).Now the question is how many people use the Gear Vr on S7 in order to remove or not.
Click to expand...
Click to collapse
Everything is in aroma except edge panel. svoice, weahter and gear vr as well
Thanks Tkkg1994 for another awesome work altough i have a doubt,why the Nougat folder on the BT/CP folder?
pbls said:
Thanks Tkkg1994 for another awesome work altough i have a doubt,why the Nougat folder on the BT/CP folder?
Click to expand...
Click to collapse
Because I uploaded nougat BL and CP
Sent from my SuperMan powered SM-G930F
SuperStock-Rom V1.1:
- Rebased on BPJG release
- November security patch
- Kernels updated with BPJE source drop and BPJG ramdisk
- Magisk phh updated to r266
- Phh updated to r266
Download V1.1 (or through OTA)
Does this rom have rom control?
bax-gold said:
Does this rom have rom control?
Click to expand...
Click to collapse
No...
Sent from my SuperMan powered SM-G930F
{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty may be void.
*
* We're not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on: TWRP v3.4.0
PitchBlack version: 3.0.0
Device: picasso (all models should work)
Picasso TG general group: https://t.me/XiaomiRedmiK30
Maintainer/Authors build: masemoel and Hadenix
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version/another recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From fastboot
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
From TWRP app
(Ideal if you don't own a PC).
Download Official TWRP app from Play Store.
Extract the PBRP zip.
Flash the recovery.img with the TWRP app.
Reboot to recovery.
Flash the whole PBRP zip (otherwise you won't have PBRP tools working properly).
Enjoy
Changelog
PBRP changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR\
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Picasso changelog
Code:
PBRP 3.0.0 2020-12-17 - Android Q and R
- Added nano editor.
- Fixed decryption issues with Android 11 (now it should decrypt even when the password is not a pattern). This makes now A11 PBRP be marked as stable!
- All PBRP changes in the latest month.
PBRP 3.0.0 2020-11-10 - Android Q and R
- Fixed errors when wiping some partitions.
- Touch delay on the first 5 seconds has gone.
- Minor touches on fstabs.
- All PBRP work in the latest week.
PBRP 3.0.0 2020-11-03 - Android Q and R
- Updated vendor, kernel and dtbo to xiaomi.eu 12.0.7.0 ones.
- Fixed wiping errors in [U]Wipe[/U] section.
- Fixed some flags in dynamic partitions.
- (Hopefully) Fixed asking decryption key when it's not needed.
- Fixed flashing failure with multiple Migrate zips.
- Fixed duplicated super partition in backup section.
- Translations updated (PBRP team) and other minor stuff by the team as well :).
PBRP 3.0.0 2020-10-03 - Android R
- Initial XDA release, based on Q tree.
PBRP 3.0.0 2020-10-03 - Android Q
- Update kernel stuff to stable MiUI 12.0.6.
- Remove DTBO partition from Wipe section (it can't be wiped).
- Some PBRP UI fixes by the team.
PBRP 3.0.0 2020-10-01 - Android Q
- Now we don't need to unmount anything before flashing.
- Translation characters are now showed correctly (fixes issue with Asian fonts not showing).
- Some UI fixes and other improvement by the PBRP team.
PBRP 3.0.0 2020-09-19 - Android Q
- Initial XDA release
Bugs
- You tell me!
- Check current issues at the GitHub Issues tracker before reporting one (it may already exist): https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/issues
Downloads
Flashable Android 10/Q zip [MEGA folder]
https://mega.nz/folder/10I1RKgC#onjHUvM4-trZ9qcfkWkLtw
Flashable Android 11/R zip [MEGA folder]
https://mega.nz/folder/EoIHDYIL#kFemXVyMKd53kKCdZm3SUg
Note that this is still experimental as Android 11 source for PBRP hasn't been still released!
Version information
Status: Stable
Created: 2020-09-19
Last updated: 2020-11-03
Beers & coffees (obviously hitting the thanks button is always enough, but this will motivate me 1000%): https://www.paypal.com/paypalme/masemoel
Little reminder here: I abandoned this project in favour of OrangeFox Recovery Project, so don't expect any updates from my side here anymore. If anyone is willing to continue this project, my trees are available as always on my GitHub (see the OP).
OrangeFox Recovery Project for picasso
Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?
Dan Ratia said:
Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?
Click to expand...
Click to collapse
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.
Dan Ratia said:
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.
Click to expand...
Click to collapse
Weird... Ensure that you have Redmi K30 5G version, and not normal K30 (aka phoenix).
Sent from my Redmi K30 5G using XDA Labs
Yes, i am sure it is Redmi K30 5G
Dan Ratia said:
Yes, i am sure it is Redmi K30 5G
Click to expand...
Click to collapse
Then it's very weird... No one has reported that the recovery is not booting on their picasso.
Did you flashed that modified vbmeta image by PeterCxy for his LineageOS recovery? (If you flashed it, then flash the original one)
Either that or your outdated vendor base would be the reason why it's not booting for you.
Sent from my Redmi K30 5G using XDA Labs
I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.
Dan Ratia said:
I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.
Click to expand...
Click to collapse
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs
Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.
ThomasRhin said:
Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.
Click to expand...
Click to collapse
Hello and thanks, Thomas.
The unofficial TWRP is being maintained by Hadenix in GitHub's picasso group right now.
Me I will stay in PBRP as I feel comfortable, safe, and has a lot of features with a nice UI ?
I once built TWRP to ensure that the device tree I did was working as it should, and also to see if an issue in PBRP was happening in TWRP as well.
https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/releases/tag/TWRP
But I won't build it anymore for now, PBRP works flawlessly + there is already another dev compiling and improving it.
Sent from my Redmi K30 5G using XDA Labs
so its only for k30 5g or it will aslo work on k30i 5g?
@tensionless said:
so its only for k30 5g or it will aslo work on k30i 5g?
Click to expand...
Click to collapse
It should work... I haven't tested though as I don't have that picasso variant
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?
Dan Ratia said:
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?
Click to expand...
Click to collapse
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
Well i wil try again, i flashed ROM, Gapps, start ROM, Format data and Magisk.
masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...
Dan Ratia said:
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...
Click to expand...
Click to collapse
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Click to expand...
Click to collapse
Ok I got it... You are flashing the forcing encryption disabler... Then you have to flash Magisk 20.3 only, and later you can upgrade if you want...
Flash it after crDroid as well
EDIT: You can look at my AICP build either in the Telegram group mentioned in the OP, or by looking at Redmi-30-5G GitHub.
Sent from my Redmi K30 5G using XDA Labs
I bring news that the new CRUEL kernel developed by Denis has very good new updates, including the addition of support for DEX in 2k quality instead of FULLHD +.
Other updates such as performance, battery optimization and additional features are also specified in ChangeLog.
Telegram Group Oficial:
CruelKernel && Magisk Debugging Modules
CruelKernel v3.9-rc1 (testing release)
Models: G970F/N, G973F/N, G975F/N G977B/N, N970F, N975F, N971N, N976B/N
OS Patch Date: 2020-11 (install script will change it if required during installation)
Build config: magisk, nohardening, force_dex_wqhd, ttl, cifs, ntfs, sdfat, nodebug, noaudit, noksm, nomodules, wireguard, usb_serial, sched_powersave, sched_performance, morosound, boeffla_wl_blocker, fake_config
Download (build with cruel toolchain):
https://cruelkernel.org/release/V3.9-rc1/CruelKernel-v3.9-rc1.zip
Alternative downloads (same config, other toolchains):
https://cruelkernel.org/release/V3.9-rc1/alt/
ChangeLog:
- G977N, G973N models added
- G970F/G975F/G973F updated to DTJA
- N976B/N970F/N975F updated to DTJ4
- Magisk v21.1 version
- vendor lock for dp cable for DEX removed (thanks, fart1-git)
- zip installer implemented
- automating os_patch_level level patching in installer (https://github.com/CruelKernel/clone_header)
New configs in sources:
- "reiser4" added for Reiser4 filesystem
reiser4progs (https://github.com/CruelKernel/reiser4progs/releases)
- "empty_vbmeta" added to include vbmeta in installer zip
- "force_dex_wqhd" - always use WQHD resolution for DEX (disable vendor check)
- "dtb" - build dtb and include them in zip installer
New cruelbuild commands:
- ./cruelbuild pack ... - to create zip installer
- mkimg is now default command for cruelbuild
- if there is no model=<MODEL> parameter, the script will try to detect model from connected by usb phone
- Multiple models: ./cruelbuild model="G973F,G975F,G970F"
- All models: ./cruelbuild model="all"
- NODEFAULTS=y ./cruelbuild +samsung ... - disable all defaults
- ./cruelbuild flash ... - removed
- FLASH=y ./cruelbuild ... - to flash img file during build
- FLASH_ZIP=y ./cruelbuild pack ... - to flash zip file during build
Github Actions changes:
- will create installer by default
- change "INSTALLER: yes" to "INSTALLER: no" if you need raw images
If you like the work and want to help me with hosting:
https://www.paypal.me/evdenis
Hitting star button on GitHub and thanks button on XDA really helps.
Thanks!
Thread closed.
You may continue this discussion in the official kernel thread located here. Thank you.
Different variants of Magisk that are available for use :
Magisk VariantStable / Beta / CanaryReleaseOfficialAndroid / OOSOOS 11 and aboveMaintainertopjohnwuProject LinkGitHubZygiskNoDenyListNoMagiskHideYesModules RepoYesDownload LinkMagisk
This tutorial will :
provide you with all the steps to root your Oneplus 9 Pro (with your bootloader already unlocked)
provide you with all the steps to unlock your Oneplus 9 Pro bootloader
provide you with all the steps to keep root during/after an OTA (system update)
provide you with a lot tricks if you have troubleshooting questions
provide you with a lot of solutions of you have softbricked your Oneplus 9 Pro
provide you with all the ways if you want to bring back your Oneplus 9 Pro to unroot & lock back the bootloader
Boot & Magisked boot images :
Boot the Magisked kernel/boot to temporarily gain root, and then once temporarily booted, patch your own kernel with direct install from Magisk application
LE2120 - China : ColorOS
LE2121 - India : DA
LE2123 - EU : BA
LE2125 - NA/Global : AA
LE2127 - T-Mobile : ACB Boot link
OxygenOS 13.1.0.500 boot : with Magisk v26.1
Untouched/Magisked (AA)
Untouched/Magisked (BA) (patched with Magisk 25.2)
Untouched/Magisked (DA) / Not yet available !
OxygenOS 13 F.75 boot : with Magisk v25.2
Untouched/Magisked (BA)
OxygenOS 13 F.21 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (DA)
OxygenOS 13 F.74 boot : with Magisk v25.2
Untouched/Magisked (BA)
OxygenOS 13 F.20 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (DA)
OxygenOS 13 F.73 boot : with Magisk v25.2
Untouched/Magisked (BA)
OxygenOS 13 F.18 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (DA)
OxygenOS 13 F.72 boot : with Magisk v25.2
Untouched/Magisked (BA)
OxygenOS 13 F.17 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (DA)
OxygenOS 13 F.16 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OxygenOS 12 C.66 boot : with Magisk v25.2
Untouched/Magisked (AA) / Not yet available !
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OxygenOS 12 C.65 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OxygenOS 12 C.64 boot : with Magisk v25.2
Untouched/Magisked (AA) / Not yet available !
Untouched/Magisked (BA)
Untouched/Magisked (DA) / Not yet available !
OxygenOS 12 C.63 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (BA) / Not yet available !
Untouched/Magisked (DA)
OxygenOS 12 C.62 boot : with Magisk v25.2
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OxygenOS 12 C.61 boot : with Magisk v25.1
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OxygenOS 12 C.48 boot : with Magisk v24.3
Untouched/Magisked (AA)
Using AA boot_patch to boot BA and DA, then direct install is recommended:
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OxygenOS 12 C.47 boot : with Magisk v24.3
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OxygenOS 12 C.44 boot : with Magisk v24 (beta but solid)
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OOS 11.2.10.10 boot :
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OOS 11.2.9.9 boot :
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OOS 11.2.8.8 boot :
Untouched/Magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OOS 11.2.7.7 boot :
Untouched/magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OOS 11.2.6.6 boot :
Untouched/magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OOS 11.2.5.5 boot :
Untouched/magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
OOS 11.2.4.4 boot :
Untouched/magisked (AA)
Untouched/Magisked (BA)
Untouched/Magisked (DA)
LE2120 - China : ColorOS
LE2121 - India : DA
LE2123 - EU : BA
LE2125 - NA/Global : AA
LE2127 - T-Mobile : ACB
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it.
Root your Oneplus 9 Pro (with Bootloader already unlocked)
Step 1 - Booting temporarily root1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 9 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
{
"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"
}
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
By booting with the patched image, you now have temporary root access. To make it permanent open Magisk app.
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 2 - Reboot and your device is now rooted !
Unlock the Bootloader and Root the OnePlus 9 ProStep 1 – Enable OEM unlockingYou need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot oem unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Step 3 - Booting temporarily root1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 9 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
Step 4 - Install magiskInstall the latest Magisk apk on your phone. Open it and:
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 5 - Reboot and your device is now rooted !
Keep Root and OTA updates
How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
For Android 12, install this APK "OPLocalUpdate_For_Android13.apk"
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Application
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !Option 2 : Booting temporarily root
For some reason, Since C63 OTA, some users have reported that on the option 1, the system rebooted byt itself after the OTA update which does not give then the option to install Magisk to the inactive slot after OTA.
If that happens, no worry just perform the Step 1 - Booting temporarily root described on "Root your Oneplus 9 Pro (with Bootloader already unlocked) Section.
Option 3: with incremental OTA Access (AA) :
Step 1 - Get back your original boot image1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 9 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !
Troubleshooting questions :
Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
If you can't install/update Netflix install the latest Netflix from apkmirror manually (like any other apk file)
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear cachesClear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Clear cache from RecoveryReboot into Recovery and select wipe CACHE. Recovery boot to be activated from Settings/System/developpers options/advanced restart. Once in Recovery select WIPE & WIPE CACHE Only !
Step 4 - Safetynet FixInstall Safetynet Fix Magisk Module
Step 5 - Look at the following guideFollow this Guide
My device has Widevine L3, how to get back L1?
Downgrading to Oos 11 using MSM Tool.
Unlock bootloader and update system flash the first OOS 12 OTA provided by the system itself.
Then update to the latest F18 (for Global and Indian devices) or F72 (for EU device) OTA using FastbootEnhance. Widevine will back to L1.
Phone Bricked ? :
Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules
Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original boot.imgIf your device can go to fastboot mode:
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash back full OTA fileIf you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 4 - Change the active slotIf your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 5 - Wipe data in Recovery mode or fastboot commandOption A : If your device can still go to Recovery mode (ie thru fastboot mode: "fastboot reboot recovery")
From Recovery Wipe data and reboot
Option B :
Code once in fastboot mode:
"fastboot- w"
Option 6 - MSMIf none of the above works then go for MSM tool
Option 1 to 4 would normally not alter your personal data, applications and own set-up
Option 5 & 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :Option 1 : Original Boot & relock with fastboot commandStep 1 - Restore orignal boot.imgOption A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original boot.
Step 2 - Relock the bootloader1. Execute the following command to proceed for bootloader unlocking: "fastboot oem lock"
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Option 2 : MSM Tool MSM tool will relock your boaloader !
Option 1 & 2 will wipe your personal data and applications
Return your phone to OOS 11 (after installing OOS 12/13) ? :
How can I downgrade my device to OxygenOS 11?:
Doing so will WIPE YOUR DATA, you are strongly advised to back it up before.
Sideload local update APK : https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Download one of the following downgrade files to go back to OxygenOS 11.2.8.8 (please take great care in selecting the region meant for your device) and move it to the root of your internal storage (where Downloads and DCIM directories are). Those files have been shared by OnePlus on previously linked OB 1 thread, and are directly linked here only for convenience.
Global: https://oxygenos.oneplus.net/OnePlu...all_2107082120_downgrade_2e0c2b9ecc3c4102.zip
EU: https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_2a8892dd474c4472.zip
India:
https://oxygenos.oneplus.net/OnePlus9ProOxygen_22.I.11_OTA_0110_all_2107082121_downgrade_66a1f653e8ee4eb5
(you have to add the .zip extension manually after downloading the file)
Launch the local update app and select the downgrade package you previously moved to the root of your device internal storage. If the downgrade package does not show up in the local update app, ensure its extension ends with .zip. Delete if .jar is there. Click on “Restart” once prompted.
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.
OnePlus 9 Pro OxygenOS 13 F.16 GLO / EU / IND
Global
Europe
India
OnePlus 9 Pro OxygenOS 12 C.48 GLO / EU / IND
System
[Optimized] the stability of communication
[Improved] system stability
[Updated] Android security patch to 2022.0
Downloads
Google OTA Server:
Global Full Edition (LE2125_11_C.48)
European Full Edition (LE2123_11_C.47)
Indian Full Edition (LE2121_11_C47)
OnePlus 9 Pro OxygenOS 12 C.47 GLO / EU / IND
System
[Optimized] the stability of communication
[Fixed] the issue of the operator's name displayed incorrectly
[Fixed] the low probability issue that unable to send MMS
[Improved] system stability
[Updated] Android security patch to 2022.0
[Optimized] the stability of communication
Camera
[Optimized] the fluency of taking pictures
Downloads
Google OTA Server:
Global Full Edition (LE2125_11_C.47)
Global Increment Edition (LE2125_11_C.44)
European Full Edition (LE2123_11_C.47)
Indian Full Edition (LE2121_11_C47)
Indian Increment (LE2121_11_C.44)
Indian Increment (LE2121_11_C.46)
OnePlus 9 Pro OxygenOS 12 C.44 GLO / EU / IND
System
• Improves system performance in some scenarios.
• Fixes a display issue with charging animations that would occur in certain scenarios.
• Fixes a display issue with the notification drawer that would occur in some gaming scenarios.
• Fixes a scrolling lag issue with the notification drawer.
Apps
• Optimizes vibration feedback for some gaming scenarios.
Camera
• Fixes an issue where Camera might sometimes crash.
• Fixes an issue where Camera might occasionally not respond when you want to take a video.
Security
• Integrates the January 2022 Android security patch to enhance system security.
Size
Full: 4.10 GB (4398423308)
Downloads
Google OTA Server:
Global Full Edition
European Full Edition
Indian Full Edition
---------------------------------------------------------------------------------------
OnePlus 9 Pro Oxygen OS 12.0.0.0.LE15 AA/ BA / DA
Changelog 12
Warning : some users report to not get network after updating...
System
Optimized desktop icons with improved textures, by using a design inspired by brand-new materials and uniting lights and layers
Dark mode
Dark mode now supports three adjustable levels, bringing a more personalized and comfortable user experience
Shelf
New additional style options for Cards, making data contents more visual and easier to read
Newly added Earphone Control Card with Bluetooth earphone one-click adjustment
Newly added access to OnePlus Scout in Shelf, allowing you to search multiple contents on your phone, including Apps, Settings, Media Data, etc
Newly added OnePlus Watch Card in Shelf, to easily glance at your health stats
Work-Life Balance
Work-Life Balance feature is now available to all users, allowing you to effortlessly switch between Work and Life mode via quick settings
WLB 2.0 now supports automatic Work/Life mode switching, based on specific locations, Wi-Fi network, and time, also bringing customized App notification profiles according to the personalization
Gallery
Gallery now allows you to switch between different layouts with a two-finger pinch gesture, intelligently recognizing the best-quality pictures, and cropping the thumbnail based on the content, making the gallery layout more pleasing
Canvas AOD
Canvas AOD brings you new diverse styles of lines and colors, for a more personalized lock screen experience with inspiring visuals
Newly added multiple brushes and strokes and support for color adjustment
Optimized software algorithm and improved face recognition to better identify the features and skin color of different figures
US version (AA)
Official link 1
Official link 2
European version (BA)
Official link 1
Official link 2
Indian edition (DA)
Official link 1
Official link 2
OnePlus 9 Pro Oxygen OS 11.2.10.10.LE15 AA/ BA / DA
System
• Optimized the third-party app experience
• Updated Android security patch to 2021.11
• Improved System stability and fixed known issues
US version (AA)
Official link 1
Official link 2
European version (BA)
Official link 1
Official link 2
Indian edition (DA)
Official link 1
Official link 2
OnePlus 9 Pro Oxygen OS 11.2.9.9.LE15 AA/ BA / DA
System
• Updated Android security patch to 2021.09
• Fixed known issues and improved stability
Camera
• Newly added XPan Mode, reproduces the preview box and unique aspect ratio of the legendary camera series "XPan". It includes two unique filter styles - 'color film', 'black and white film' and a 'film processing imitation' effect that recreates the classic elements of retro shooting experiences
US version (AA)
Official link 1
Official link 2
European version (BA)
Official link 1
Official link 2
Indian edition (DA)
Official link 1
Official link 2
OnePlus 9 Pro Oxygen OS 11.2.8.8.LE15 AA/ BA / DA
System
• Updated Android security patch to 2021.07
• Fixed known issues and improved stability
Ambient Display
• Newly added Bitmoji AOD, co-designed by Snapchat & Bitmoji, which will liven up the ambient display with your personal Bitmoji avatar. Your avatar will update throughout the day based on your activity and things happening around you ( Path: Settings - Customization - Clock on ambient display - Bitmoji )
OnePlus Store
• An intuitive and convenient way to manage your OnePlus account, get easy-to-access support, discover exciting members-only benefits, and shop for OnePlus products. (Please note that it can be uninstalled)
US version (AA)
MEGAsync link (full OTA)
Official link (full OTA)
Official Link 1 (OTA Incremental from 7.7. AA)
European version (BA)
MEGAsync link
Official link 1
Official link 2
Indian edition (DA)
Official link 1
MEGAsync link
OnePlus 9 Pro Oxygen OS 11.2.7.7.LE15 AA/ BA / DA
System
• Reduced power consumption in specific scenarios
• Fixed known issues and improved stability
Camera
• Newly added HDR option in video recording interface（Path: Menu options in the upper right corner of the screen-Dynamic video）
• Improved the shooting and recording experience
US version (AA)
Official link 1
European version (BA)
MEGAsync link
Official link 1
Indian edition (DA)
Official link 1
Official link 2
OnePlus 9 Pro Oxygen OS 11.2.6.6.LE15 AA/ BA / DA
System
• Improved charging experience
• Optimized power consumption
• Fixed known issues and improved stability
Camera
• Improved the hidden operation logic of the camera‘s top bar
• Optimized the noise reduction and sharpening effect of the rear camera
• Improved the focusing experience and brightness constancy in indoor scenes
• Improved the accuracy of auto white balance of the rear camera
Network
• Improved network performance
US version (AA)
Not yet available
European version (BA)
MEGAsync link
Official link 1
Indian edition (DA)
Official link 1
Official link 2
OnePlus 9 Pro Oxygen OS 11.2.5.5.LE15 AA/ BA / DA
System
• Improved charging performance
• Fixed the small probability lagging issue of keyboard
• Fixed known issues and improved system stability
• Updated Android security patch to 2021.05
Camera
• Improved the HDR effect in some shooting scenes
• Improved the white balance performance of the rear camera
Network
• Improved the stability of network communication
• Improved the performance of Wi-Fi connection
US version (AA)
Not yet available
European version (BA)
Official link 1
Official link 2
Indian edition (DA)
Official link 1
Official link 2
OnePlus 9 Pro Oxygen OS 11.2.4.4.LE15 AA/ BA / DA
System
• Improved charging stability
• Improved the sensitivity of the keyboard in the edge area
• Improved the temperature control strategy
• Fixed the issue that the battery icon in the status bar is abnormally displayed
• Fixed the small probability issue that Google Fi SIM card can not accept incoming calls
• Fixed known issues and improved system stability
• Updated Android security patch to 2021.04
• Updated GMS package to 2021.03
Camera
• Improved the image purity and the ambiance performance
• Improved the white balance consistency of the rear camera
• Improved image over-sharpening of the rear camera
US version (AA)
Official link 1
European version (BA)
Official link 1
Official link 2
Indian edition (DA)
Official link 1
Official link 2
Hithere, I need a full package of Oxygen OS for oneplus9pro.
Can u help me with that?
Thx
Thank bro
So it is possible to boot this bootimage and then root OP9P with Magisk?
Hoping we see the full zip for global soon! Just got my 9 Pro today but getting impatient to root! xD
Damn, nothing for Global yet eh...
Fulbring said:
Damn, nothing for Global yet eh...
Click to expand...
Click to collapse
You can download the EU stock boot.img that's in this thread (2nd post), download the latest magisk canary manager and patch that boot.img. Then you can temporarily gain root by rebooting to bootloader and booting that image ex. "fastboot boot boot.img"( your boot.img name will vary after patching). After the phone boots you can just go into magisk manager and do a "direct install" and that will patch your global boot.img to gain permanent root.
ecera said:
You can download the EU stock boot.img that's in this thread (2nd post), download the latest magisk canary manager and patch that boot.img. Then you can temporarily gain root by rebooting to bootloader and booting that image ex. "fastboot boot boot.img"( your boot.img name will vary after patching). After the phone boots you can just go into magisk manager and do a "direct install" and that will patch your global boot.img to gain permanent root.
Click to expand...
Click to collapse
Thank you so much!! This appears to work perfectly for me.
Ensure you guys patch your own boot.img, but you can use the EU boot.img linked in post #2 just fine on AA/Global/US variant.
Now to figure out how to pass CTS..
ecera said:
You can download the EU stock boot.img that's in this thread (2nd post), download the latest magisk canary manager and patch that boot.img. Then you can temporarily gain root by rebooting to bootloader and booting that image ex. "fastboot boot boot.img"( your boot.img name will vary after patching). After the phone boots you can just go into magisk manager and do a "direct install" and that will patch your global boot.img to gain permanent root.
Click to expand...
Click to collapse
What a Chad! Will do this! I hate not having root from the get go.
Are ya'll passing safety net? What am I missing? CTS profile doesn't pass but basic integrity does.
Would this be due to patching boot.img with the EU ROM, since I am on a global variant?
Only thing I can think of..
Reddit3321 said:
Are ya'll passing safety net? What am I missing? CTS profile doesn't pass but basic integrity does.
Would this be due to patching boot.img with the EU ROM, since I am on a global variant?
Only thing I can think of..
Click to expand...
Click to collapse
Here's a screenshot of my cts. I patched with the temp EU root as well.
Reddit3321 said:
Are ya'll passing safety net? What am I missing? CTS profile doesn't pass but basic integrity does.
Would this be due to patching boot.img with the EU ROM, since I am on a global variant?
Only thing I can think of..
Click to expand...
Click to collapse
Nope, working just fine for me. Make sure you have system less host enabled. Perhaps that's why.
Weird, I just re tried the whole root process again and I’m still failing CTS. I think maybe I’ll just wait until global patched_boot.img is available until trying again as I can’t figure out what exactly I’m missing.
Reddit3321 said:
Weird, I just re tried the whole root process again and I’m still failing CTS. I think maybe I’ll just wait until global patched_boot.img is available until trying again as I can’t figure out what exactly I’m missing.
Click to expand...
Click to collapse
Go to Settings / applications / delete data cache GMS and Playstore / then reboot
Steve0007 said:
Go to Settings / applications / delete data cache GMS and Playstore / then reboot
Click to expand...
Click to collapse
Still didn't work for me
I think I may just wait and try again once global is out.
Edit:
I think I figured it out. I was flashing boot.img instead of *booting* boot.img
Still not working for me Not sure what it is I'm doing wrong at this point.
ecera said:
You can download the EU stock boot.img that's in this thread (2nd post), download the latest magisk canary manager and patch that boot.img. Then you can temporarily gain root by rebooting to bootloader and booting that image ex. "fastboot boot boot.img"( your boot.img name will vary after patching). After the phone boots you can just go into magisk manager and do a "direct install" and that will patch your global boot.img to gain permanent root.
Click to expand...
Click to collapse
Apologies if this is a silly question - does it matter which software version my US phone is on or will this work regardless?
NSD said:
Apologies if this is a silly question - does it matter which software version my US phone is on or will this work regardless?
Click to expand...
Click to collapse
I'm pretty sure that you'll be fine on whichever version your OP9 pro is on. From previous experience I've learned that if there is a major gap between firmware versions that you're temporarily booting and what's installed on the phone then you might run into issues, such as phone not booting the temp boot img or it will boot, but with no wifi ect.. Good thing it's just a temporary boot.. You can still do the direct install method and you should be fine.
ecera said:
I'm pretty sure that you'll be fine on whichever version your OP9 pro is on. From previous experience I've learned that if there is a major gap between firmware versions that you're temporarily booting and what's installed on the phone then you might run into issues, such as phone not booting the temp boot img or it will boot, but with no wifi ect.. Good thing is just a temporary boot.. You can still do the direct install method and you should be fine.
Click to expand...
Click to collapse
Cool thanks. Even though there's no twrp I should still be able to get back to stock through fastboot or recovery presumably should anything actually go wrong.
Reddit3321 said:
Still didn't work for me
I think I may just wait and try again once global is out.
Edit:
I think I figured it out. I was flashing boot.img instead of *booting* boot.img
Still not working for me Not sure what it is I'm doing wrong at this point.
Click to expand...
Click to collapse
I'm thinking since you flashed the EU boot instead of booting... You're most likely still on that EU boot.img. That could be causing your issues.