Motorola Stock Kernel with f2fs patched and kcal added
Disclaimer: Your warranty is now void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Why this kernel exists:
As many of you know, there is a bug with the f2fs filesystem in the stock kernel which makes it nearly impossible to use systemless modifications (SuperSU, Magisk) on the Moto Z Play. The flaw and its solution are described here.
I started this project for myself to be able to use systemless modifications again, but I hope some of you will find it useful as well. The kernel for Android 6.0 is based on Motorolas source code release (MPN24.104-44) from here and includes security fixes up to december 2016. The Android 7.0 kernel is based on release MMI-NPN25.137-15 with patch date 2017-01. It has been developed and tested with the European model and ROM, but should work on other variants as well as all retail models share the same boot image.
As of patch level 2017-03, Motorola included the f2fs fix in the official kernel. However, I will continue to work on this kernel for those of you who need the verifiedbootstate patch and kcal.
Warning
This kernel is not meant for 7.1.1 and will break your camera and probably more! Once Motorola release the source code you will find an update here.
Features:
f2fs patched to allow systemless modifications to work
kcal color control
Thats all for now, let me know if you need something else ...
Instructions:
If you previously rooted your phone with the chinese TWRP in system mode I would advise to un-root the phone from the SuperSU app and restore a factory image. However, deleting userdata is not necessary except for the SuperSU app. It might not recognize the new systemless mode otherwise.
Optional, unroot via SuperSU app
Reboot to boatloader / fastboot mode
Flash modified TWRP image Flash @Alberto97 latest TWRP from here
Reboot directly into recovery
Optional, remove forced encryption (see below)
Check with TWRP file manager that /data/.supersu is not present, otherwise delete the file.
Flash kernel zip
Flash SuperSU
Reboot the device
Remove forced encryption (optional):
Download attached RemoveForceEnc.zip
Flash file from TWRP
Wipe userdata (in TWRP or use 'fastboot erase userdata' in fastboot mode)
Credits:
Thanks to @Alberto97 for his work on addison.
Thanks to @erfanoabdi and @ryzion for the RemoveForceEnc.zip found on the Moto Z forum (in this post).
@fortunz for testing kcal functionality
Download:
03/22/2017 - Android 7.0.0 Kernel v03: Mega
03/23/2017 - Android 6.0.1 Kernel v03: Mega
Archive:
Modified TWRP: androidfilehost No longer needed, flash latest TWRP from @Alberto97
02/18/2017 - Android 7.0.0 Kernel v02: androidfilehost, Mirror: Mega
02/02/2017 - Android 6.0.1 Kernel v02-test: androidfilehost
01/28/2017 - Android 6.0.1 Kernel v01: androidfilehost
Sources: Github
Changelog:
03/22/2017 | 6.0.1 / 7.0.0 | v3
Added kcal color control. Patch
02/18/2017 | 7.0.0 | v2
Remove verifiedbootstate flag to pass SafetyNet checks. Patch
02/17/2017 | 7.0.0 | v1
Initial release for 7.0
02/02/2017 | 6.0.1 | v2-test
Test build to pass safetynet checks. Removes verifiedbootstate flag. See this patch
01/28/2017 | 6.0.1 | v1
Initial release based in MPN24.104-44 and security bulletins up to december 2016
Is it just enough to flash the sprasechunks ? Is there any need to delete userdata?
Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.
tomparr said:
Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.
Click to expand...
Click to collapse
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.
flashallthetime said:
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.
Click to expand...
Click to collapse
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?
Thanks a lot OP, I've been waiting for something like this. I'll give it a go.
tomparr said:
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?
Click to expand...
Click to collapse
No I didn't.
Edit: You need to also re-flash the kernel as well as the sparsechunks. It works and I'm rooted with SR3.
Sent from my XT1635-02 using XDA-Developers Legacy app
Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
{
"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"
}
regards
So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app
elgringoloco77 said:
So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, running AdAway (and Titanium Backup) was the main reason I started building the kernel.
iron maiden said:
Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
regards
Click to expand...
Click to collapse
Depends, if you are ok with system mode root, you don't need this.
tomparr said:
Depends, if you are ok with system mode root, you don't need this.
Click to expand...
Click to collapse
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards
iron maiden said:
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards
Click to expand...
Click to collapse
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Main advantage is that Magisk is supposed to work, and that f2fs is working properly.
Systemless root already does work fine using phh superuser without this kernel.
To have AdAway functionality - which systemless needs SuperSU or Magisk, both don't work without this kernel - you may use dns66 which does not modify hosts, but instead runs a local DNS server. It has very similar functionality and doesn't even need root.
I'd like to have f2fs working, but currently don't have the time to do backup, restore in twrp doesn't work maybe because of broken f2fs, do 4 times update etc. This kernel probably will help me and I thank you very much for publishing it. We'll see when I find the time to test it.
tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification
iron maiden said:
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification
Click to expand...
Click to collapse
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?
iron maiden said:
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?
Click to expand...
Click to collapse
You can use the regular SuperSU and Magisk versions from here and here.
tomparr said:
You can use the regular SuperSU and Magisk versions from here and here.
Click to expand...
Click to collapse
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
Unistalled Sr3 v279 and installer phhsupersu
regards
iron maiden said:
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
regards
Click to expand...
Click to collapse
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.
tomparr said:
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.
Click to expand...
Click to collapse
Hello ok very very thanks for job
regards
Related
This ROM is a genuine CM13 build from source for the Elephone Trunk. It's based on mdeejay's Ark Benefit code with modifications by @BlueFlame4 and @hisname. The source code is available on GitHub.
Working:
Phone
Mobile data in dual-sim configuration
Wifi
GPS
Bluetooth
Audio
Known Bugs:
Torch tile in the status bar is not available
Haptic feedback on soft buttons
XDA:DevDB Information
CM13 for Elephone Trunk, ROM for all devices (see above for details)
Contributors
ottmi, siljaer
Source Code: https://github.com/ottmi/android_device_elephone_trunk
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20160902
Beta Release Date: 2016-09-02
Created 2016-06-07
Last Updated 2016-09-02
Changelog
20160902
First try to fix sdcard issues, will need more testing
Fix thermal-engine to actually start
Fix audio_effects.conf
Tweak auto-brightness
Enable OTA updates
Use Wileyfox Swift blobs for everything but camera
Update to latest CM13 source
20160816
Enable thermal-engine to fix overheating emergency shutdowns
Update kernel to latest MSM8916 to fix Quadrooter vulnerabilities
Re-enable AEC audio effects
Update to latest CM13 source
20160811
Revert changes to mixer_paths.xml and audio_effects.conf to fix echo problems
Update to latest CM13 source
20160803
Update to latest CM13 source to fix surfaceflinger crashes
20160803
Tweak GPS settings to obtain faster locks
Enable input event for headphone jack
Use ACDB libraries from Wileyfox swift, fix some ACDB-related settings
Update to latest CM13 source
20160722
Incorporate @siljaer's modifications to mixer_paths.xml to fix echoes and low volume audio recordings
Pull in additional permissions to reflect actual hardware of the phone (light & proximity sensor)
Change screen density to 300dpi
Backport LZ4 compression from Linux 3.12 for use in ZRAM
Try to fix Torch problems by restarting media service after full boot
Update to latest CM13 source
20160708
Fix wpa_supplicant crashes
Update to latest CM13 source
20160706
Switch to generic CyanogenMod MSM8916 kernel
Use Wileyfox Swift kernel configuration as template
Increase partition sizes of system and data to 1.8GB and 12GB
Update to latest CM13 source
20160630
Fix bug in libstagefright properly
Fix sensor glue code to only show actually existing sensors
Fix device permissions
Use own key to sign code instead of testkeys
Set selinux to enforce
Update to latest CM13 source
20160616
Fix mediaserver crashes to a bug in libstagefright (roll back to commit 8f270dc)
Use Adreno binary blobs from Wileyfox Swift (which are more complete)
Update to latest CM13 source
20160614
Enabling of Qualcomm Fluence as suggested by @Bingo Bronson
Backport of the F2FS driver from Linux 3.12
Enabling of LTE as preferred network on 2nd SIM card as well
Some changes to the auto brightness thresholds
Update to latest CM13 source
20160611
Enable haptic feedback on soft keys
Change default device name for wifi direct and hotspot to "Trunk" (not Benefit!)
Update to latest CM13 source
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source
Flashing Instructions
You will have to disable the bootloader lock first:
Enable developer options in Android by tapping the Build version in Settings > About 7 times
Check "Enable OEM unlock"
Next you will have to boot into TWRP, use @hisname's TWRP:
http://forum.xda-developers.com/gen...410-5-inch-t3177753/post66208281#post66208281
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash recovery twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.
Installation Xposed Rom Ottmi
Installation Xposed Rom Ottmi
@ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work
josoft86 said:
Installation Xposed Rom Ottmi
@ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work
Click to expand...
Click to collapse
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?
josoft86 said:
I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64
ottmi said:
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.
ottmi said:
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source
Click to expand...
Click to collapse
Great, so many thanks, but, the link?
marcachas said:
Great, so many thanks, but, the link?
Click to expand...
Click to collapse
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
{
"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"
}
Visit xda with your browser if you are currently on xda labs or some kind of forum app.
Bingo Bronson said:
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
Visit xda with your browser if you are currently on xda labs or some kind of forum app.
Click to expand...
Click to collapse
Oh, thanks, you are the best, this rom is so table and smooth, your job is awesome, a hug.
Thank you. I decided to buy the Elephone Trunk because I was interested in a economic phone that could 'easily' be upgraded with non stock ROM (preferably CM 13).
I have gone through the previous conversation and I must admit I'm impressed with your progress so far. Congratulations and a big thank you!
I will definitely flash your build as soon as I receive the phone.
Enviado desde mi Nexus 5 mediante Tapatalk
Great job!
Great job and super useful guide @ottmi.
Thank you!
I am currently running your previous release (cm-13.0-20160515-UNOFFICIAL-trunk) and have no issues to report at all!
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
Thank you for the excellent work.
Kind regards.
P.S. I have downloaded and installed GAPPS (Google Apps) from CM portal and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.
kbezerianos said:
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
[...] and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.
Click to expand...
Click to collapse
Dirty flash is enough, no need to clean everything. Just install the new build, wipe the caches afterwards like it is suggested by TWRP recovery.
Some of your apps may have a survival script, others need to be reflashed (this is just the case for special tools, like Xposed, etc.)
Nano Gapps is a smart choice either way, because all the pre-installed Gapps will be outdated soon enough, so why bother to install a "huge" Gapps pack...
I use microG and have roughly 260 MB left on the system partition.
Bingo Bronson said:
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.
Click to expand...
Click to collapse
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
But, but... I'm also on 3.0.2-0 and the Xposed zips & ROMs, for example, are processed without error, Aroma installer is also supported...
Who compiled / ported your TWRP version? I used only @hisname releases and they never let me down. ?
ottmi said:
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.
Click to expand...
Click to collapse
I didn't even consider that possibility, since it has been mentioned numerous times in the old thread, ignorance is bliss (on my side), ahem...
I'm out of "thanks" to give, so I'll "upvote for awareness" later...
josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.
ottmi said:
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash boot twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.
Click to expand...
Click to collapse
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!
One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Enviado desde mi Nexus 5 mediante Tapatalk
21prods said:
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!
Click to expand...
Click to collapse
Bummer. You're right, I've fixed the instructions accordingly. Sorry for that!
21prods said:
One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Click to expand...
Click to collapse
I'm using a 32GB microsdhc to store music and pictures, no issues at all. I've also used 64GB mirosdxc without problems. I've never tried moving apps though.. How does it show in Settings->Storage & USB?
Yes, that's it. There you have the possibility of formatting the SD card to use it as (more) internal memory.
Enviado desde mi Nexus 5 mediante Tapatalk
{
"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"
}
This is only for Huawei P9 (EVA)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-eva.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.1-1/twrp-3.1.1-1-eva.img"][U]download twrp-3.1.1-1-eva.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-03-01
Last Updated 2017-06-11
Changelog
Code:
[B]TWRP 3.1.1-0[/B]
* bump up TWRP version to 3.1.1
* fix backup of /version
* use device specific and updated prebuilts (+kernel)
* remove the ability to flash images to ext4 mounted partitions
[B]TWRP 3.1.0-3[/B]
* kernel updated for proper loop support
* magisk can now be installed and is supported by every rom running b380+ kernel (tested on b383)
* native_package.xml has been changed to device specific version
[B]TWRP 3.1.0-2[/B]
* Add support for NTFS formatted MicroSD cards or OTG drives
* Enabled direct image flashing to special partitions
(be careful when using it - one wrong klick means brick in a second!)
* TWRP is now compatible with AOSP based ROMS (LineageOS)
and decrypted Stock ROMS, transition from Stock to LOS is possible.
* Correct versioning - Device version is now comming from the common base.
* 3650-common: introduce init.recovery.hi3650.power.rc for better power handling
[B]TWRP 3.1.0-1[/B]
* proper handling of decryption (improves booting time by ~10 seconds)
* do not wipe /data/hw_init during /data wipe or factory reset to prevent system errors
* cleanup ramdisk, reduced image size by 10mb
[B]TWRP 3.1.0-0[/B]
* add the ability to format oem specific partitions
* add back f2fs support so we can format /data as f2fs
* bump up twrp version to 3.1.0
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
frenzissi said:
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
Click to expand...
Click to collapse
Yes, should be fine
Atarii said:
Yes, should be fine
Click to expand...
Click to collapse
I can confirm this works fine
Thanks
<<<by scaniathe>>>
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
LE: I flashed @Atarii B378 img and now I am rooted. AdAway is working as expected. Thank you!
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
OldDroid said:
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
Click to expand...
Click to collapse
The one from here https://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947. Dont waste your time. Its working if B378 img from Atarii is flashed.
Atarii said:
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
Click to expand...
Click to collapse
L09 B378 img is ok for now. Still need to test if system apps uninstall. But I am happy Adaway is working!
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Perfect!
Thanks
cbgti said:
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Click to expand...
Click to collapse
Encryption/decryption support is related to the /data partition (where your user files are stored). The encryption scheme changed for Nougat, so this is the first TWRP that supports being able to read/write to that encrypted /data partition.
Read-only system mode (aka systemless mode) - some people do not touch the system partition, so they can later apply OTAs easier (as they perform a diff on system files)
good job OpenKirin team, thx a lot
So supersu from chainfire isn't working even on this, right?
@Atarii : Thanks!
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
maliniaka said:
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
Click to expand...
Click to collapse
Propably the script wont work on huawei, but we work on it.
will this TWRP work for the Honor 6x Nougat Beta too?
sassmann said:
will this TWRP work for the Honor 6x Nougat Beta too?
Click to expand...
Click to collapse
what does the title say, whats the name of the forum where this has been posted?
Hope this answers everything!
PS: Its comming soon for H6X.
{
"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"
}
This is only for Honor 8 (FRD)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-frd.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_frd/releases/download/3.1.1-1/twrp-3.1.1-1-frd.img"][U]download twrp-3.1.1-1-frd.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which H8 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=4960686"]OldDroid[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8
Contributors
surdu_petru, XePeleato, OldDroid
Source Code: https://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-03-03
Last Updated 2017-06-26
Changelog
Changelog
Code:
[B]TWRP 3.1.0-2[/B]
* Add support for NTFS formatted MicroSD crads or OTG drives
* Enabled direct image flashing to special partitions
([B][I][COLOR="Red"]be careful when using it - one wrong klick means brick in a second![/COLOR][/I][/B])
* TWRP is now compatible with AOSP based ROMS (LineageOS)
and decrypted Stock ROMS, transition from Stock to LOS is possible.
* Correct versioning - Device version is now comming from the common base.
* 3650-common: introduce init.recovery.hi3650.power.rc for better power handling
*** reserved ***
surdu_petru said:
*** reserved ***
Click to expand...
Click to collapse
Thanks for putting the effort into making and sharing this TWRP with us.
The download link isn't working for me.
I'm using the mobile XDA labs
Thanks
John
Sent from my Honor 8 using XDA Labs
johnhux7 said:
Thanks for putting the effort into making and sharing this TWRP with us.
The download link isn't working for me.
I'm using the mobile XDA labs
Thanks
John
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Yes, it's working ... just checked right now ! You should try one of the alternate mirror links./ Or use a PC for download !
surdu_petru said:
Yes, it's working ... just checked right now ! You should try one of the alternate mirror links./ Or use a PC for download !
Click to expand...
Click to collapse
OK.
I will try in a PC when I can.
On a mobile the hyperlink doesn't show so there is nothing to click on
Got it to download.
Just had to open the page in a browser.
Thanks buddy
Sent from my Honor 8 using XDA Labs
Has anyone managed to root EMUI 5 using this recovery?
Thnak you so much surdu_petru
surdu_petru said:
Yes, it's working ... just checked right now ! You should try one of the alternate mirror links./ Or use a PC for download !
Click to expand...
Click to collapse
The link is working.
Great work @surdu_petru!!!!! once again!
Regarding this. I already have previous nougat twrp + root (although no access to data partition) Can I just flash this one on top? Do I need to format or reinstall something afterwards?
[EDIT]
Just replace previous 3.0.2 for nougat and everything is working: root and access to data & system partition! Enormous work!!!!
Another thing, you mention a "modded boot image with disabled dm-verity" can you explain what's this and for what is it used for?
Thanks once again!
@surdu_petru : Thanks for the great work. I'm curious if you used the 7.x.x kernel from the OP git here https://github.com/OpenKirin/android_kernel_huawei_frd/tree/7.x ? If so, did you use recommended-config? (with loop-dev == y)?.
Many thanks.
Wow. Just wow.
@surdu_petru Thanks for your work, but i´m not able to mount data partition
flashed over twrp 3.0.2.0 for Nougat
4rch0 said:
@surdu_petru Thanks for your work, but i´m not able to mount data partition
flashed over twrp 3.0.2.0 for Nougat
Click to expand...
Click to collapse
Happened to me too. Maybe we need to reflash to full stock again to bring back encryption, then flash this TWRP. I don't wanna run the whole process again. Guess I'll just have to wait for LOS14.1 to be stable.
thank you so much!! now i can root (may be)..
4rch0 said:
@surdu_petru Thanks for your work, but i´m not able to mount data partition
flashed over twrp 3.0.2.0 for Nougat
Click to expand...
Click to collapse
Depends on if you formated partition before it might cause issues
Sent from my ALE-L21 using Tapatalk
LastStandingDroid said:
Depends on if you formated partition before it might cause issues
Sent from my ALE-L21 using Tapatalk
Click to expand...
Click to collapse
no didn´t format it , with the other twrp , i dont have any issues
I have flashed twrp 3.0.3 FRD at my Mate 8. I able to enter twrp but in 5 seconds my phone automatic restart. If I quickly check my internal storage. It's decrypted. So means it's working.
Is there any chance to support mate 8 too? Been using Twrp 3.0.2 FRD from beginning and has no issue.
Thanks in advance.
dexz said:
I have flashed twrp 3.0.3 FRD at my Mate 8. I able to enter twrp but in 5 seconds my phone automatic restart. If I quickly check my internal storage. It's decrypted. So means it's working.
Is there any chance to support mate 8 too? Been using Twrp 3.0.2 FRD from beginning and has no issue.
Thanks in advance.
Click to expand...
Click to collapse
If u have any chance a log would be needed. And if u can Unmount data before reboot it might help to prevent recovery from being killed
Also there might be some issues due to different devices loading recovery faster? I can't answer on this. You'll have to wait or participate in helping out testing builds from devs
Sent from my CUBOT_MANITO using Tapatalk
---------- Post added at 08:32 PM ---------- Previous post was at 08:27 PM ----------
4rch0 said:
no didn´t format it , with the other twrp , i dont have any issues
Click to expand...
Click to collapse
Where you able to use data partition in twrp earlier versions means u wiped data partition so it's decrypted. This mounts data to dm-0 if decrypted. Which the other version never did
Sent from my CUBOT_MANITO using Tapatalk
dexz said:
I have flashed twrp 3.0.3 FRD at my Mate 8. I able to enter twrp but in 5 seconds my phone automatic restart. If I quickly check my internal storage. It's decrypted. So means it's working.
Is there any chance to support mate 8 too? Been using Twrp 3.0.2 FRD from beginning and has no issue.
Thanks in advance.
Click to expand...
Click to collapse
your device isnt supported, its for honor 8!
Regards,
OD
TWRP installed. Data encrypted. But flashing EMUI5 root with the package found here did not give any success (root not detected)
morpheus302 said:
TWRP installed. Data encrypted. But flashing EMUI5 root with the package found here did not give any success (root not detected)
Click to expand...
Click to collapse
Yes I can confirm that. @LastStandingDroid could you upload your old TWRP?
{
"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"
}
SuperSU 2.82 for EMUI 5
Note: SuperSU 2.82 working on EMUI 5 but may not on EMUI 5.0.1 or 5.1
Here is updated SuperSU-2.82-SR5 for EMUI5.0.1
This will work (tested) on EVA (Huawei P9) - based on original SuperSU SR5 by @Chainfire
Download: https://www.androidfilehost.com/?fid=673956719939815322
MD5: b168a88bc815d3fac521ace97402a949
Older Versions here: (Thread will get general update soon)
SuperSU-2.82-EMUI5
Changelog: First 4 Versions based on original Chaifires SuperSU 2.82 code with mounting vendor and search for boot_a. These versions are without additional modification by phh superuser files/scripts
The second 3 Versions (a/b) - 09.06.2017 01:17- are mixed with phh superuser and original Chaifires SuperSU Code (same as 2.79 for EMUI): Download-Links below - for Firmwares before b38x and without loop support
Current Status: STABLE
NOTE: If your device has no Root - just flash it with the related TWRP for your device! - But if your device is rooted with previous Versions of SuperSU for EMUI, dont flash it over existing Root but make the steps written below "How do Root"
4 Versions based on original Chainfire SuperSU 2.82 code - 07.06.2017
Succesful tested on P9 b383, b386 and Mate 9, also working on Honor 6x BLN-B360 - but may work also on other devices from Firmwares b38x up and new Nougat Firmwares for Devices, which had Marshmallow until short time ago.
It will probably not work on other Firmwares before b38x (for these devices are the modified versions with mixed code from SuperSU and phh Superuser)
1) SuperSU-v2.82-EMUI5-SELEnforcing.zip
Just added init.d script, but let's SELinux as it is.
Download: https://www.androidfilehost.com/?fid=673368273298961353
MD5: 18529db8978a39212db335ad006760cf
2) SuperSU-v2.82-EMUI5-SELPermissive.zip
Added init.d script and set SELinux permanently to permissive (required for Viper4Android)
Download: https://www.androidfilehost.com/?fid=817550096634775861
MD5: 57a081ba3ba03691c4ffaf9ab141a44e
3) SuperSU-v2.82-EMUI5-KangV-Roms.zip
Added init.d script, SELinux Permissive, Script for K-Settings
Download: https://www.androidfilehost.com/?fid=817550096634775860
MD5: 5e68f7b1175f7b51d64802f7416a04f5
4) SuperSU-v2.82-without-additive.zip - try out, if none of the three above works (its without additional features, just Root)
Download: https://www.androidfilehost.com/?fid=961840155545571636
MD5: bfa6f458949f6deb056044b0337ef31a
3 Versions (a/b) mixed with original Chainfire SuperSU 2.82 code and pph superuser code - 09.06.2017
For devices which has no Loop Support yet, but working also on devices, which can succesful use Version 1, 2, 3 and 4.
Kirin 960 based Devices must use Version 6 a/b and 7
Following versions are not compatible with AOSPA based Roms.
5. Version comes in 2 editions (5a and 5b) - should work with devices which have fully working TWRPs - like P9
Version 5/a - Name: SuperSUv2.82-EMUI5-dm-verity-Enforcing.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=961840155545572192
MD5: 0da8bcbf0eb164c7512ae083012b45eb
About:
dm-verity and dm-crypt enabled
init.d Support
SELinux Enforcing
Version 5/b - Name: SuperSUv2.82-EMUI5-dm-verity-Permissive.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=817550096634776377
MD5: 14a0ac7fd3a725ee326e9944399a916e
About:
dm-verity and dm-crypt enabled
init.d Support
permanent SELinux Permissive
Version 5 (a/b) is working (tested) on:
Huawei P9
Huawei P9 Lite
Huawei Mate 8
Huawei Mate 9
Honor 8
Not working:
Huawei Honor 8 FRD-L09C432B380
Huawei P10 and P10 plus - must have noverity version
6. Version comes in 2 editions - for Kirin 960 based Devices like P10 and P10+ and should work with other devices which have NOT properly working TWRPs
Version 6/a - Name: SuperSUv2.82-EMUI5-noverity-Enforcing.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=889764386195906385
MD5: a37380d6f1659f78bbd341954ed804b2
About:
dm-verity DISABLED
init.d Support
SELinux Enforcing
Version 6/b - Name: SuperSUv2.82-EMUI5-noverity-Permissive.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=889764386195906386
MD5: 99f06e5fe34b93409d558fc119d15e59
About:
dm-verity DISABLED
init.d Support
permanent SELinux Permissive
Version 6 (a/b) is working (tested) on:
Huawei P10+
Huawei P10
Huawei Mate 9
Huawei P8 Lite 2017
Huawei Honor 8 FRD-L09C432B386
7. Version comes in 2 editions - special for KangV-ROMs on Kirin 960 based Devices.
Version 7/a - Name: SuperSUv2.82-EMUI5-dm-verity-KangV.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=745425885120739007
MD5: 8ca92c52a338fd82e923d0479769e23a
Version 7/b - Name: SuperSUv2.82-EMUI5-noverity-KangV.zip
Download for testing issues: https://www.androidfilehost.com/?fid=889764386195906387
MD5:0df87e5c4a5d41a0ed8b21085a33a6e8
About:
Version 7/a = dm-verity and dm-crypt enabled
Version 7/b = dm-verity disabled
init.d Support
script for K-Settings
script for busybox in /system/xbin
permanent SELinux Permissive
Version 7/a is working (tested) on:
KangV Roms
Huawei Mate 8
Huawei P9
Version 7/b is not tested yet!
PREVIOUS FINAL VERSION 2.81 - mixed code with chainfires and phh superusers - was working on most Huawei Devices:
https://www.androidfilehost.com/?w=files&flid=183923
How Do Root:A) You need unlocked Bootloader and the TWRP related for your device installed!
TWRP for Huawei P9 Nougat you can find here - with Decryption Support by Recognized Developer OldDroid: https://forum.xda-developers.com/p9/development/twrp-t3565703
B) Look into your settings: Developer options must be enabled and inside: ADB Debugging and USB Debugging, as well as in settings/advanced settings/security "Allow unknown sources" PC should have the driver installed for connecting Phone in Fastboot Mode.
C) Make a TWRP Backup of - boot.img - data - system -vendor - before flashing SuperSUfor EMUI 5 - if one version dont work on your Huawei Device as it should, restore original boot.img with TWRP and try one of the other versions.
Note: If your Phone is not rooted -just flash SuperSU 2.81 EMUI 5 and reboot - Phone boots up two times and with the second boot you come back to your homescreen with Root.
If your Phone is rooted und you want update SuperSU - dont flash over existing Root, do following steps:
1) Copy SuperSU-2.82.zip to your external SD
2) Make a Complete Unroot from SuperSU App!
3) SuperSU ask: "Should SuperSU restore original boot.img" - check YES (2 times)
4) Phone reboots - dont wait but in the moment your screen is black press VOL+ Button and hold it the whole time until you are booted to TWRP.
5) In TWRP go to install and select SuperSU 2.82, swype to install
6) Search on Homescreen for SuperSU App and open it - look if you're done - if yes =good
NEXT STEPS ONLY IF ROOTING WAS NOT SUCCESFUL OR IF SUPERSU APK CANNOT UNROOT OR RESTORE BOOT.IMG:
Flash original (unmodified) boot.img with Fastboot - or restore boot.img from the Stock TWRP Backup (boot) of same Firmware
- if restored from TWRP Backup, dont restart system, go back and - flash SuperSU
- if flashed instead with Fastboot - disconnect USB from Device and with Power and VOL+ boot to TWRP and flash SuperSU
Note 2: If you are own the SuperSU PRO Version - you have just to update the SuperSU-Pro.apk directly from SuperSU "Upgrade to Pro Version". You will redirected to Playstore, install the Update!
If your Phone has a Custom Rom like Nougat KangV Rom - you can try to flash over existing Root - if it dont work (its different: for most will work, for some not) you can do:
Unroot with following steps:
0) KangV Roms for Nougat come with prerooted boot.img. SuperSU 2.82 should be able to patch and update it - just try.
If the update fails it would be good to find (or have) the original unmodified boot.img for the Firmware on which Rom is based and restore this.
1) Look into your settings: Developer options must be enabled and inside: ADB Debugging and USB Debugging, as well as in settings/advanced settings/security "Allow unknown sources" PC should have the driver installed for connecting Phone in Fastboot Mode.
2) Copy SuperSU 2.82 EMUI 5 to your external SD
3) Open old or not properly working SuperSU and make a "complete Unroot" - when SuperSU ask you 2 times "Do you want to restore original boot.img" check: YES
Maybe it is successful - perhaps not - if yes:
4) Phone reboots - but it cannot reboot to system!!
5) Instead booting to system you come into Huawei eRecovery - just make SHUTDOWN.
Now same steps, if the restore of original boot.img was not succesful - you must restore original (unmodifiied) boot.img from Firmware. If you have a TWRP-Backup from unrooted original boot.img restore it and go to 8) - if you have not a TWRP Backup for restore - go to step 6)
6) Connect Phone with USB to PC and with Vol- and Power start Phone into fastboot mode.
7) Flash unmodified boot.img with Minimal ADB and Fastboot. Disconnect phone from USB.
8) Press VOL+ with the finger of your left hand and press it all the time and with the finger of your right hand press Power Button.
9) Phone boot up and soon as Huawei Logo is shown on screen, release the Power Button but stay pressing VOL+ the whole time until you are in TWRP.
10) Flash SuperSU 2.82 EMUI 5
11) Phone boots up now two times and will finally boot to system.
12) search for SuperSU on Homescreen - its not on your usual place, its somwhere else on homescreen - open it and you should have now clean SuperSU 2.82
Do this steps just, if you had problems with flashing 2.82
Please report if you rooted your device successful / not succesful - and give information about your Device-model, Build number, TWRP-Version (fully or not properly working, ist it able to mount data with f2fs, make backup and restore?...)
Credits:
@Chainfire - SuperSU
@CCMT - SuperSU Release
@phhusson - phh's SuperUser/ OpenSource SELinux-capable SuperUser
@OldDroid - TWRP for P9 Android 7 with Decryption Support
@ante0 - Mate 9 Development
@Telperion - Honor 8 Development
Thank you
Thanks for the great job.
how do you root it if it's still not rooted? I lost root when I upgraded to nougat and never found out how to get it back
Thanks for job, but 2.81 version is really works? Because the 2.79 is not fully good: there was 1 problem: doesn't delete system programs with the Titanium Backup.
kazshizka said:
how do you root it if it's still not rooted? I lost root when I upgraded to nougat and never found out how to get it back
Click to expand...
Click to collapse
You just need the right TWRP and then flash SuperSU zip, reboot phone without wipe of Dalvik /Cache
Which phone model to you have?
Shyciii said:
Thanks for job, but 2.81 version is really works? Because the 2.79 is not fully good: there was 1 problem: doesn't delete system programs with the Titanium Backup.
Click to expand...
Click to collapse
You need also a good busybox 1.26.2 - I always use the one from YashdSaraf (xda)
Tecalote said:
You need also a good busybox 1.26.2 - I always use the one from YashdSaraf (xda)
Click to expand...
Click to collapse
SuperSU must works without busybox. My friend modified the SuperSU version 2.79, and it works fully.
Tecalote said:
You just need the right TWRP and then flash SuperSU zip, reboot phone without wipe of Dalvik /Cache
Which phone model to you have?
Click to expand...
Click to collapse
My phone is a P9, Model is EVA L-19. So i need to flash TWRP first? I just used a one click program the last time I rooted it so I'm too sure how to do stuff
kazshizka said:
My phone is a P9, Model is EVA L-19. So i need to flash TWRP first? I just used a one click program the last time I rooted it so I'm too sure how to do stuff
Click to expand...
Click to collapse
You need this TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703
And after flash with this TWRP this SuperSU and you are rooted
If you don't know how to flash TWRP, search related Thread
Tecalote said:
You need this TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703
And after flash with this TWRP this SuperSU and you are rooted
If you don't know how to flash TWRP, search related Thread
Click to expand...
Click to collapse
Many Thanks!!!!
Shyciii said:
SuperSU must works without busybox. My friend modified the SuperSU version 2.79, and it works fully.
Click to expand...
Click to collapse
This SuperSU works fully - but we talked about TitaniumBackup and this would may work better with Busybox.
Root without Busybox is like a tree without leaves.
I have not tested yet, if SuperSU works in case of TitaniumBackup without Busybox.
But you can test it by yourself.
And if your friend make it better let him do this Job - but don't discuss with me about Busybox
Shyciii said:
Thanks for job, but 2.81 version is really works? Because the 2.79 is not fully good: there was 1 problem: doesn't delete system programs with the Titanium Backup.
Click to expand...
Click to collapse
I have the same issues but these might be unrelated to the most recent SuperSU version. I cannot uninstall system apps and I can't "frost" system apps in Titanium Backup (I have pro version).
Also some other root apps don't work correctly like:
https://play.google.com/store/apps/details?id=de.andip71.screenoff&hl=de
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol&hl=de
clouds5 said:
I have the same issues but these might be unrelated to the most recent SuperSU version. I cannot uninstall system apps and I can't "frost" system apps in Titanium Backup (I have pro version).
Also some other root apps don't work correctly like:
https://play.google.com/store/apps/details?id=de.andip71.screenoff&hl=de
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol&hl=de
Click to expand...
Click to collapse
I make some tests in the evening on Stock Firmware with this SuperSU and will report you how to do
For PRO SuperSU is one more information in OP (OP updated)
cant freeze apps?
Terminal:
su
setenforce 0
done
xtcislove said:
cant freeze apps?
Terminal:
su
setenforce 0
done
Click to expand...
Click to collapse
Good idea to set temporarily SELinux from Enforcing to Permissive. :good:
I made also second version of SuperSU 2.81 for EMUI 5, which enables SELinux durable to permissive.
But I didn't post it here.
I don't know if people would like to have this.
Tecalote said:
Good idea to set temporarily SELinux from Enforcing to Permissive. :good:
I made also second version of SuperSU 2.81 for EMUI 5, which enables SELinux durable to permissive.
But I didn't post it here.
I don't know if people would like to have this.
Click to expand...
Click to collapse
Give it to me
xtcislove said:
Give it to me
Click to expand...
Click to collapse
Okay, in the later evening. I am at work now (Job)
Soon I come home
Give me too
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
scaniathe said:
Give me too
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Yeah, I will update Thread with both versions and Users can choose
{
"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"
}
I am not affiliated with the official Evolution-X ROM developers
Updated for October 2022
Signed with my own keys
some features you may be used to from this ROM are not available (yet), I'm assuming it just takes time for the developers to add them to the still relatively new Android 13/tiramisu. If I have time, I'll see what I can do.If something is missing, it's not due to me excluding anything.
The Camera and Bluetooth are working fine now, I noticed in my last version I posted here last week for 220905 they were broken.
Kernel Source
Device, Kernel and Vendor Repos
Downloads
Instructions:
Flash the vendor_boot and boot
Sideload the ota in recovery
thank you
Can I flash from android 12?
Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I think so but I was on stock Google 13 when I did mine.
Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.
twykomantis said:
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.
Click to expand...
Click to collapse
I personally haven't noticed a large drain in battery while idle on a13 evo-x but I did have that problem before I updated directly from 12. I put com.android.hbmsvmanager on restricted battery usage and it solved the problem. Maybe this will help on 13??
HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
EDIT: got it fixed, reflashed all the other stock partitions via flash.bat
Raz0Rfail said:
HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
Click to expand...
Click to collapse
Did you flash vendor_boot image with correct command?
Yep:
fastboot.exe flash boot boot.img --slot all
fastboot.exe flash vendor_boot vendor_boot.img --slot all
But I fixed it and thanks for the fast response .
just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/
Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.
elong7681 said:
Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.
Click to expand...
Click to collapse
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can
DroidRommer said:
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can
Click to expand...
Click to collapse
Thanks for the response
To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks
DroidRommer said:
To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks
Click to expand...
Click to collapse
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
As long as you flash the latest safety net fix module in magisk you'll be fine
DroidRommer said:
just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/
Click to expand...
Click to collapse
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.
aleph.mercury said:
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.
Click to expand...
Click to collapse
Thank you for this! I really appreciate you integrating that module for calling. Sorry I had no idea about the safety net thing Its pretty much just habit for me to flash the module in magisk at this point lol. Just cuz you mentioned kernels is there any chance there will be anymore cpu governors added in the future such as interactivex or anything like it? I like tweaking everything lol
I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique
aleph.mercury said:
I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. then build the kernel. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique
Click to expand...
Click to collapse