Well we had root for a while and it's been great! But we loose safetynet goodies (this is individual) and the ease to use great mods without messing with the system partition.
Don't worry this is no more needed!
Before following this procedure make sure to back up everything you want to save because we gonna wipe data partition!
Edit the twrp files are slightly modified to suite honor 8 pros partition layout. As they where originally for mate 9 it had to be done.
Installation instructions.
1.backup everything you want to save on your internal storage.
2. Download https://mega.nz/#F!mwJVAaaR!Nh_NZ8jCmp76VGVWC-WPbg and extract it on your external storage.
3. Extract magisk-root.zip and flash twrp-magisk-H8P.img using fastboot using this command: fastboot flash recovery_ramdisk twrp-magisk-H8P.img
4. Flash fstab-decrypt.zip which will replace fstab in vendor/etc/
5. FORMAT DATA in twrp.
6. (optional) boot system and set everything up.
7. Reboot to recovery and flash Magisk.zip
8. Wait and see
UPDATE INSTRUCTIONS
Open Magisk manager settings
Press update channel > custom and enter
https://goo.gl/jefZKH
You'll get latest Magisk for huawei devices
Credits firedance1961 at www.android-hilfe.de for providing files.
TopJohnwu for magisk
Source: https://www.android-hilfe.de/forum/...c432-data-mod-v-magisk-root-fstab.857097.html
This has been tested on both EMUI 8.0 and AOSP treble build and works fine!
{
"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"
}
Q/A
Safetynet doesn't pass! You lied!
It does but magisk hide is being disabled on boot. Just trigger the Magisk hide and safetynet will pass.
Does it work on encrypted devices?
NO as of now it doesn't. It doesn't patch the ramdisk properly. But it's being worked on!
Sent from my DUK-L09 using Tapatalk
Its working and passes safetynet too. :good: How can I again encrypt my device? I can't able to access my internal files from mobile or PC.
LastStandingDroid said:
Q/A
Safetynet doesn't pass! You lied!
It does but magisk hide is being disabled on boot. Just trigger the Magisk hide and safetynet will pass.
Does it work on encrypted devices?
NO as of now it doesn't. It doesn't patch the ramdisk properly. But it's being worked on!
Click to expand...
Click to collapse
Hey man. I tried rooting and it worked. But selinux stays on enforcing and I can't get Magisk modules to work. Any workaround?
Sent from my Honor 8 Pro using XDA Labs
arunpkrt said:
Its working and passes safetynet too. :good: How can I again encrypt my device? I can't able to access my internal files from mobile or PC.
Click to expand...
Click to collapse
Simply by flashing https://mega.nz/#!zp4wgQDL!ZRj0MFdpZ8hB_ve1gKUoOCcfDqzG2fxWZaJ3o3dxXe8
It's the original file
jinchuuriki12 said:
Hey man. I tried rooting and it worked. But selinux stays on enforcing and I can't get Magisk modules to work. Any workaround?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Unfortunately this is disabled within kernel so we'd have to wait for a custom kernel.
Sent from my DUK-L09 using Tapatalk
It looks like you only need to wipe data before installing Magisk and not actually decrypt. So thus who want to use Magisk with encryption
Wipe data/factory reset in twp should do it and install Magisk after wipe .
At least it worked on aosp
Sent from my DUK-L09 using Tapatalk
Can anyone try to install without actually decrypt?
Method would be
1. Wipe data factory reset
2.flash Magisk
This worked on aosp so should work on emui too
Sent from my DUK-L09 using Tapatalk
@LastStandingDroid
willing to try your root solution. need the exact flashcommand to wich partition i can flash the twrp-magisk.img. thanks
kurvenmeister said:
@LastStandingDroid
willing to try your root solution. need the exact flashcommand to wich partition i can flash the twrp-magisk.img. thanks
Click to expand...
Click to collapse
recovery partition name has changed in oreo.
command is "fastboot flash recovery_ramdisk ***.img"
---------- Post added at 01:52 PM ---------- Previous post was at 01:47 PM ----------
Thanks for such quick solutions. Works perfectly. Passes safetynet too. Just 1 issue for me - the selinux mode is stuck on enforcing.
I need permissive selinux mode to run Root Call Blocker. I would appreciate it if you could fix it.
kurvenmeister said:
@LastStandingDroid
willing to try your root solution. need the exact flashcommand to wich partition i can flash the twrp-magisk.img. thanks
Click to expand...
Click to collapse
recovery_ramdisk
devilrulz4ever said:
recovery partition name has changed in oreo.
command is "fastboot flash recovery_ramdisk ***.img"
---------- Post added at 01:52 PM ---------- Previous post was at 01:47 PM ----------
Thanks for such quick solutions. Works perfectly. Passes safetynet too. Just 1 issue for me - the selinux mode is stuck on enforcing.
I need permissive selinux mode to run Root Call Blocker. I would appreciate it if you could fix it.
Click to expand...
Click to collapse
We must use a custom kernel for it now so it seems. As Huawei disabled it by default.
Sent from my DUK-L09 using Tapatalk
@ laststandingdroid
thanks an sorry, i did not read the op carefully, where it is written on. according to post nr. 7 flashing fstab is no longer needed?
---------- Post added at 01:39 PM ---------- Previous post was at 01:16 PM ----------
That's what I want to get tested.
I wiped aosp flashed Magisk (successfully) and it worked. I want confirmation of emui users though
Sent from my DUK-L09 using Tapatalk
am on aosp vanilla by phhusson. test an report tonight.
first test done. xposed seems to run perfect. xprivacylua is running. installing recovery was as usual very easy. flashing magisk without format data gave me "error 1". formatted data, installed magisk, xposed and xprivacylua. until now everything seems to work as it should.
@LastStandingDroid
congrats, good job
device is still encrypted. creating a backup ends with error 255.
@LastStandingDroid
flashing fstab seems to be still necessary to stay decrypted?
kurvenmeister said:
am on aosp vanilla by phhusson. test an report tonight.
first test done. xposed seems to run perfect. xprivacylua is running. installing recovery was as usual very easy. flashing magisk without format data gave me "error 1". formatted data, installed magisk, xposed and xprivacylua. until now everything seems to work as it should.
@LastStandingDroid
congrats, good job
device is still encrypted. creating a backup ends with error 255.
@LastStandingDroid
flashing fstab seems to be still necessary to stay decrypted?
Click to expand...
Click to collapse
Yeah as Magisk doesn't patch it. You should only be needed to factory reset to flash Magisk so u won't loose /data/hw_init edit on 3.0.3 u still do
Sent from my DUK-L09 using Tapatalk
you mean the magisk zip or the fstab zip?
kurvenmeister said:
you mean the magisk zip or the fstab zip?
Click to expand...
Click to collapse
Magisk zip doesn't patch fstab as its moved from boot
Sent from my DUK-L09 using Tapatalk
After I flashed "fstab-decrypt.zip" on AOSP treble the SIM indicator showed "no SIM". Although, I could still receive SMS/calls but no outgoing.
On EMUI 8 it works fine.
devilrulz4ever said:
After I flashed "fstab-decrypt.zip" on AOSP treble the SIM indicator showed "no SIM". Although, I could still receive SMS/calls but no outgoing.
On EMUI 8 it works fine.
Click to expand...
Click to collapse
Don't use decrypted data partition on aosp
Sent from my DUK-L09 using Tapatalk
A new version is out
Do not use stable or beta channel as it will break boot! Do following procedure below
15.4(1541)
To update open settings > chanel > custom
https://goo.gl/jefZKH
Enjoy thanks ante0 for the tip!
Sent from my DUK-L09 using Tapatalk
I'm currently using honor 8 pro oreo version with twrp and mmagisk install. how do i update honor 8 pro oreo version when new update version come out? I want to update and keep user data intact. Can someone post me a tutorial? thanks
Related
is now depreciated visit:
TWRP 3.0.3 with decyption support!
Your warranty is probably void. Do we care?
THIS IS NOT A FINAL RELEASE! IF ANYTHING GOES WRONG IT ISN'T MY FAULT! THIS IS NOT BUILT FROM SOURCE, IT USES RENEWED KERNEL FROM N AND EDITED FSTAB! AND DO NOT USE DATAFIX U CAN FORMAT DATA PARTITION IN ADVANCED WIPE!
HOW-TO ROOT YOUR MATE 9/P9/Honor 8
Download
Phh su r275 version and flash
Download and install Material phh apk: Release post
Done!
What's new
MTP auto mount on boot fixed!
Data unmount after few seconds fixed.
Bugs
Data Decryption
Battery status
Mounting Loop Devices (Kernel doesn't support this)
Credits: TWRP (Team win Recovery Project)
Huawei
@BadWolfYe for giving info on how he got MTP working.
Me
Current status:Stable
Stable: Sort OF
Created: 2016-11-20
Something
unable to flash anything as its saying no storage
nintendolinky said:
unable to flash anything as its saying no storage
Click to expand...
Click to collapse
I noticed
You need to flash one zip
Just make sure you backup all data on your internal storage since it'll wipe it
Here it is https://mega.nz/#!SgpTiRaJ!7vLP2bLrDfbQ4eWb_Tzevlv3_Nwx2SpwvJx4iBKb9s0
You might need to wipe it after again.
Just make sure you resize the partition afterwards.
Sent from my FRD-L09 using Tapatalk
TWRP Recovery is working, SuperSU in the TWRP can not flash?
{
"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"
}
TWRP, delete Cache & Dalvik takes very long?
Formating Cache using make_ext4fs...
Hen Ry said:
TWRP Recovery is working, SuperSU in the TWRP can not flash?
View attachment 3944122 View attachment 3944123 View attachment 3944124 View attachment 3944125 View attachment 3944126 View attachment 3944127 View attachment 3944128
TWRP, delete Cache & Dalvik takes very long?
Formating Cache using make_ext4fs...
Click to expand...
Click to collapse
No you can't flash supersu for now.
I don't feel like twrp takes long time to wipe unless battery is low
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
No you can't flash supersu for now.
I don't feel like twrp takes long time to wipe unless battery is low
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
http://androiding.how/huawei-mate-8-nougat-root-twrp/ -> How to Root Huawei Mate 8 Nougat update with SuperSU
Again the B552 update.zip and the update_data_full_all_cn.zip installed in the TWRP.
Despite the factory reset (the TWRP was started), the data are still available.
The very slow formatting existed already times in an earlier TWRP version.
In the latest version for EMUI 4 / 4.1 it was very fast again.
Hen Ry said:
http://androiding.how/huawei-mate-8-nougat-root-twrp/ -> How to Root Huawei Mate 8 Nougat update with SuperSU
Again the B552 update.zip and the update_data_full_all_cn.zip installed in the TWRP.
Despite the factory reset (the TWRP was started), the data are still available.
The very slow formatting existed already times in an earlier TWRP version.
In the latest version for EMUI 4 / 4.1 it was very fast again.
Click to expand...
Click to collapse
Problem is when it tries to mount the su image it reboots.
Sent from my FRD-L09 using Tapatalk
Working in Mate 8 NXT-L29C432?
Hi Hen Ry, you mentioned 'TWRP recovery working' is on Mate 8 NXT-L29C432 please? I want to give a try.
______________________
Able to port the above TWRP on Mate 8 NXT-L29C432 successfully and boot to TWRP recovery.
SuperSU failed to flash (tried both SR3 and SR4 of SuperSU-v2.7
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Very slow formatting?
NXT-L29 with Tapatalk
Hen Ry said:
Very slow formatting?
NXT-L29 with Tapatalk
Click to expand...
Click to collapse
As I feel it. No
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Click to expand...
Click to collapse
Looking forward to it. Thank you
LastStandingDroid said:
A new TWRP version will be coming later today, which fixes the .img mount issue. now most parts are working as it should. only stuff is MTP and ADB which seems to be still broken
Click to expand...
Click to collapse
Will this fix the Bluetooth issue?
Sent from my FRD-L04 using XDA-Developers mobile app
manny18pr said:
Will this fix the Bluetooth issue?
Sent from my FRD-L04 using XDA-Developers mobile app
Click to expand...
Click to collapse
has nothing to do with the bluetooth, but yes it can apply it
could you build this for the Huawei P9? pleeaaseee! we have no working TWRP for the P9 nougat beta.
the phones are nearly identical so it should not need much adaption.
you would be our hero and your thanksmeter will explode!
Bluetooth, NFC and DUAL SIM Manager works for me.
with update_data_full_all_cn.zip
Do you have an eta for the build?
UnchartedRd said:
Do you have an eta for the build?
Click to expand...
Click to collapse
Hmm, not sure yet, still have some things i want to check first.
Hen Ry said:
Bluetooth, NFC and DUAL SIM Manager works for me.
with update_data_full_all_cn.zip
Click to expand...
Click to collapse
:good:
paratox said:
could you build this for the Huawei P9? pleeaaseee! we have no working TWRP for the P9 nougat beta.
the phones are nearly identical so it should not need much adaption.
you would be our hero and your thanksmeter will explode!
Click to expand...
Click to collapse
Sure if u have the stock recovery.img for it i can fix a fast backport
LastStandingDroid said:
Sure if u have the stock recovery.img for it i can fix a fast backport
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B9gJ44ME0ZkcSFdySTNBeTlZeTA
if you need someone to test pm me!
Unofficial release -TWRP recovery for the Galaxy J3 2017 - SM-J327U EXYNOS 7570
{
"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"
}
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA(testing)
Features:
TOUCHSCREEN working
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest nougat source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
IMPORTANT: THIS DEVICE EMPLOYS DM-VERITY. ANY MODIFICATIONS TO THE SYSTEM WILL TRIGGER DM-VERITY CAUSING A BOOT LOOP.
AFTER FLASHING TWRP DM-VERITY WILL NEED TO BE DISABLED BY FLASHING SUPERSU OR MAGISK.
ALTERNATIVELY FOLLOW THE INSTRUCTIONS BELOW TO INSTALL THE BOOT PATCH.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-j327u_271117
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption, dm-verity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Testing Stage
Please note:
I don't own this device so this is as yet untested. Please report any issues in as much detail as possible. Screenshots always welcome.
0 touchscreen functionality.
I can't get past the Swipe to Unlock screen which means I can't get past step 1 in the overall process xD
CSMNT said:
0 touchscreen functionality.
I can't get past the Swipe to Unlock screen which means I can't get past step 1 in the overall process xD
Click to expand...
Click to collapse
No worries. I had an idea this might be the case as I had the same issue on the J330F and had to fix the issue on that device also.
The 2 devices are fairly similar.
In the meantime an otg mouse should work.
Working perfect on SM-J327U???
Fdraco10 said:
Working perfect on SM-J327U???
Click to expand...
Click to collapse
It will be at some point today after the update to fix the touch screen.
ashyx said:
It will be at some point today after the update to fix the touch screen.
Click to expand...
Click to collapse
Oh ok! Please, I beg You, I need flash my SM-J327U :crying::crying::crying::crying::crying:
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
ashyx said:
It will be at some point today after the update to fix the touch screen.
Click to expand...
Click to collapse
Yeah, please fix it! I need Root my SM-J327U :crying::crying::crying::crying:
Fdraco10 said:
Oh ok! Please, I beg You, I need flash my SM-J327U :crying::crying::crying::crying::crying:
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Yeah, please fix it! I need Root my SM-J327U :crying::crying::crying::crying:
Click to expand...
Click to collapse
Touchscreen fixed build is up.
ashyx said:
Touchscreen fixed build is up.
Click to expand...
Click to collapse
Really works??
ashyx said:
Touchscreen fixed build is up.
Click to expand...
Click to collapse
Thank you, kind sir! Flashing it now.
Edit:
Touch screen is fixed. Now we have boot loop. Slowly making progress lol.
CSMNT said:
Thank you, kind sir! Flashing it now.
Edit:
Touch screen is fixed. Now we have boot loop. Slowly making progress lol.
Click to expand...
Click to collapse
What do you mean a boot loop? Is that from TWRP or SuperSU?
Please post the recovery log and more details.
ashyx said:
What do you mean a boot loop? Is that from TWRP or SuperSU?
Please post the recovery log and more details.
Click to expand...
Click to collapse
I think that boot loop is for SuperSU! I wanna try flashing the TWRP but I don´t know if I will have bootloop
Fdraco10 said:
I think that boot loop is for SuperSU! I wanna try flashing the TWRP but I don´t know if I will have bootloop
Click to expand...
Click to collapse
You can always flash the stock recovery to recover.
If you get a boot loop I'll post it up.
ashyx said:
You can always flash the stock recovery to recover.
If you get a boot loop I'll post it up.
Click to expand...
Click to collapse
Do you have link for Stock ROM for SM-J327U??
---------- Post added at 06:07 PM ---------- Previous post was at 05:50 PM ----------
@ashyx
Dude, Do you have teh stock recovery for SM-J327U??
Fdraco10 said:
Do you have link for Stock ROM for SM-J327U??
---------- Post added at 06:07 PM ---------- Previous post was at 05:50 PM ----------
@ashyx
Dude, Do you have teh stock recovery for SM-J327U??
Click to expand...
Click to collapse
Of course I'll post it if you need it.
ashyx said:
Of course I'll post it if you need it.
Click to expand...
Click to collapse
Yeah, I need it please, and so thanks!
Fdraco10 said:
Yeah, I need it please, and so thanks!
Click to expand...
Click to collapse
Why do you need it?
You can download it below:
https://desktop.firmware.mobi/device:1795/firmware:13890/download/recovery.tar/landing
ashyx said:
why do you need it?
You can download it below:
https://desktop.firmware.mobi/device:1795/firmware:13890/download/recovery.tar/landing
Click to expand...
Click to collapse
really!!!! So thanks dude!!! Thankkkkssss!!!
ashyx said:
Why do you need it?
You can download it below:
https://desktop.firmware.mobi/device:1795/firmware:13890/download/recovery.tar/landing
Click to expand...
Click to collapse
Just getting back to you now. I think the bootloop is caused by TWRP because I haven't even attempted to flash SuperSU.
My process:
I move SuperSU and the no-verity file over to my internal storage before flashing TWRP in Odin. I flash TWRP. I reboot into recovery. Touch screen works but I can't mount internal storage to flash no-verity or SuperSU. I reboot and instead of being asked to reset it's just a boot loop.
Flashed the stock rom.
CSMNT said:
Just getting back to you now. I think the bootloop is caused by TWRP because I haven't even attempted to flash SuperSU.
My process:
I move SuperSU and the no-verity file over to my internal storage before flashing TWRP in Odin. I flash TWRP. I reboot into recovery. Touch screen works but I can't mount internal storage to flash no-verity or SuperSU. I reboot and instead of being asked to reset it's just a boot loop.
Flashed the stock rom.
Click to expand...
Click to collapse
Yeah, same here bro!
Hi all!
For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch between custom and stock roms simply wasn't good enough for me. After lots of searching around, failed attempts, and some guidance by @Xennet, @osm0sis, and @nathanchance (thank you all for your help), I finally got a working solution. Ironically, it was under my nose the whole time.
@topjohnwu figured much of this out a while ago with his magiskboot binary - just modify the fstabs. Magiskboot only works for fstabs in the ramdisk though and dm-verity and forceencrypt are only disabled under certain conditions (when you create a .magisk file with the variables set to false and place it in the proper location). So I made an installker with AK3 by @osm0sis and used a combination of sed patches by @jcadduono in addition to others I found for fstabs not in the ramdisk, modified magiskboot with some extra entries I found need to be removed on some devices, and added some stuff of my own like the creation of .magisk and .supersu files in the right location with the proper contents.
The end result: a zip that will remove dm-verity and/or forceencrypt from all fstabs on your device
It can also remove disk quota if you choose. This may be needed if you have an older twrp and/or want to downgrade to Nougat. More info here: https://source.android.com/devices/storage/faster-stats
Instructions:
The zipname tells the installer what to do. Here are the current options:
Add 'enfec' or en'forceencrypt' to zipname to keep forceencrypt enabled if present
Add 'fec' or 'forceencrypt' to zipname to disable forceencrypt (zipname already has this so remove these if you want to keep it enabled)
Add 'quota' to zipname to disable disc quota
Note that verity is always disabled - it has to be for any modifications with this mod
If you're currently encrypted:
BACKUP YOUR INTERNAL STORAGE TO YOUR PC
Format data (this is NOT the same as Wipe data) (In TWRP: Wipe -> Format Data)
Reboot back into recovery
Follow the directions below for when you're not encrypted
If you're not encrypted: flash all of your stuff, then FLASH THIS ZIP LAST
Some extra details for Slot devices:
Flash ROM
Flash TWRP Installer Zip
Reboot into TWRP
Flash everything else
Flash this zip
Only difference here is the twrp zip and the recovery reboot, main principle is the same - FLASH THIS ZIP LAST
Troubleshooting:
Take a recovery log after flashing this zip (thanks to @aIecxs for the imgs):
{
"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"
}
If the zip isn't patching any fstabs that it should be, then it's possible that the previous zip(s) didn't unmount system and/or vendor properly. Either unmount them in twrp, or just reboot back into recovery and flash this zip again
Compatibility: Any android device
Source: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt
Download
Zackptg5 said:
Hi all!
For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch between custom and stock roms simply wasn't good enough for me. After lots of searching around, failed attempts, and some guidance by @Xennet, @osm0sis, and @nathanchance (thank you all for your help), I finally got a working solution. Ironically, it was under my nose the whole time.
@topjohnwu figured much of this out a while ago with his magisk installer. However, dm-verity and forceencrypt (fec) are only disabled under certain conditions (when you create a .magisk file with the variables set to false and place it in the proper location). This would be fine for magisk users, but not for everyone else. So I took Magisk 16.6 beta zip, modified it to add fstab patches by @jcadduono, added some stuff of my own, and then gutted all of the magisk stuff unrelated to this.
The end result: a zip that will remove dm-verity and fec from your boot img and fstab files (without installing magisk, I took all of that out).
Instructions:
If you're currently encrypted: BACKUP YOUR INTERNAL STORAGE TO YOUR PC. Then format data. Reboot back into recovery
After doing that or if you're not encrypted: Flash your rom, custom kernel and/or root (like magisk or supersu), then this zip.
This zip should probably be flashed after anything that modifies your boot img (magisk, supersu, other root solutions, custom kernel, etc.).
Compatibility: Any device magisk is compatible with
Source:https://github.com/Zackptg5/Disable_Dm-Verity_FEC
Click to expand...
Click to collapse
Hi!
Just to be sure, does this remove the need to flash patched boot.img files when updating stock ROMs with root?
Thanks!
Sent from my OnePlus 3T using XDA Labs
@Zackptg5 Thanks for the zip! I trust this will work for both -- Treble and non-Treble ROMs, yes?
rippledrums said:
Hi!
Just to be sure, does this remove the need to flash patched boot.img files when updating stock ROMs with root?
Thanks!
Click to expand...
Click to collapse
Not sure what you mean. This does patch the boot img to remove verity/fec though if that's what you're getting at
shadowstep said:
@Zackptg5 Thanks for the zip! I trust this will work for both -- Treble and non-Treble ROMs, yes?
Click to expand...
Click to collapse
Yup
Zackptg5 said:
Not sure what you mean. This does patch the boot img to remove verity/fec though if that's what you're getting at
Click to expand...
Click to collapse
I found this because I saw your post in @Xennet's thread for OP3/3T Oxygen OS patched boot.img files.
Currently every time I update OOS I flash a boot.img patched by him and also a zip by him as well. What I'm asking is if your zip would be enough?
Sent from my OnePlus 3T using XDA Labs
rippledrums said:
I found this because I saw your post in @Xennet's thread for OP3/3T Oxygen OS patched boot.img files.
Currently every time I update OOS I flash a boot.img patched by him and also a zip by him as well. What I'm asking is if your zip would be enough?
Click to expand...
Click to collapse
Oh, gotcha. Ya, this zip handles that so you don't need to flash the boot img anymore
Zackptg5 said:
Oh, gotcha. Ya, this zip handles that so you don't need to flash the boot img anymore
Click to expand...
Click to collapse
Awesome, thanks! :laugh:
Sent from my OnePlus 3T using XDA Labs
@Zackptg5 First of all, great job. This looks very impressive and I appreciate the work you've done. I know this will be very useful for people trying things like the P GSI image then going back to no treble ROMs back on Oreo. I was just wondering though, as I have no intention on trying any treble ROMs, is there any benefit to using this over the old no verity V2 zip for someone that will only use non-treble Oreo ROMs. Thank you
DEVILOPS 007 said:
@Zackptg5 First of all, great job. This looks very impressive and I appreciate the work you've done. I know this will be very useful for people trying things like the P GSI image then going back to no treble ROMs back on Oreo. I was just wondering though, as I have no intention on trying any treble ROMs, is there any benefit to using this over the old no verity V2 zip for someone that will only use non-treble Oreo ROMs. Thank you
Click to expand...
Click to collapse
It really depends on the rom. If you're on a custom rom the old zip is probably fine (but not always, lots of variation there). If you're on a stock or stock based rom however, this is needed (unless you flash a patched boot.img - but why flash 2 things when you can flash 1?). This zip works with treble and nontreble roms by the way and the old zip can be easily modified the same way (I have one floating around xda somewhere).
Assuming you're on a custom rom which already has dm-verity disabled, the benefit to this zip is that not only does it disable force encryption in the vendor fstabs (like the old zip), but it also disables it in the boot img which some roms have
Zackptg5 said:
It really depends on the rom. If you're on a custom rom the old zip is probably fine (but not always, lots of variation there). If you're on a stock or stock based rom however, this is needed (unless you flash a patched boot.img - but why flash 2 things when you can flash 1?). This zip works with treble and nontreble roms by the way and the old zip can be easily modified the same way (I have one floating around xda somewhere).
Assuming you're on a custom rom which already has dm-verity disabled, the benefit to this zip is that not only does it disable force encryption in the vendor fstabs (like the old zip), but it also disables it in the boot img which some roms have
Click to expand...
Click to collapse
So basically it is a more well-done version if you want to put it that way. Works on stock and custom ROMs including treble no matter what it is or if there is dm-verity enabled or not is what I'm understanding from this. I'm using treskmod currently which is basically OmniRom. I'll give it a go when I get back off holiday so I can clean flash. Thanks again?
DEVILOPS 007 said:
So basically it is a more well-done version if you want to put it that way. Works on stock and custom ROMs including treble no matter what it is or if there is dm-verity enabled or not is what I'm understanding from this. I'm using treskmod currently which is basically OmniRom. I'll give it a go when I get back off holiday so I can clean flash. Thanks again?
Click to expand...
Click to collapse
I wouldn't call it more well done but rather more complete
And yup, should work on any rom/device magiskboot is able to work with (which is most of them). Dm-verity will be removed too by this mod by the way
@Zackptg5 hi. Tell me please how need me right do. I am on LOS 15.1 on my Samsung Tab A SM-T585.now. And with dm-verity and fec are all right. But when i go on custom rom based on stock 8.0(port) i got dm-verity and fec issue. After installation this rom and start i can see all files of internal memory in file explorer. But only i reboot to recovery internal memory have size 0mb. So my question: i need do fomat data before installtion rom and your zip or only install zip?
Zackptg5 said:
I wouldn't call it more well done but rather more complete
And yup, should work on any rom/device magiskboot is able to work with (which is most of them). Dm-verity will be removed too by this mod by the way
Click to expand...
Click to collapse
@DEVILOPS 007 I just flashed latest 20180719 tresk and tried this zip and got sent back to TWRP. Immedietly flashed v2 and it booted. It worked on AOSiP earlier though so not sure what could cause it to fail here.
Sent from my OnePlus5T using XDA Labs
repey6 said:
@Zackptg5 hi. Tell me please how need me right do. I am on LOS 15.1 on my Samsung Tab A SM-T585.now. And with dm-verity and fec are all right. But when i go on custom rom based on stock 8.0(port) i got dm-verity and fec issue. After installation this rom and start i can see all files of internal memory in file explorer. But only i reboot to recovery internal memory have size 0mb. So my question: i need do fomat data before installtion rom and your zip or only install zip?
Click to expand...
Click to collapse
You'll need to format data. Then flash rom and kernel, then this after
bdwilk said:
@DEVILOPS 007 I just flashed latest 20180719 tresk and tried this zip and got sent back to TWRP. Immedietly flashed v2 and it booted. It worked on AOSiP earlier though so not sure what could cause it to fail here.
Click to expand...
Click to collapse
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Click to expand...
Click to collapse
Format data everytime or just once for this to work or format because of treble or what? I'm curious as to when formatting is required and why exactly.
Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Click to expand...
Click to collapse
I'll do it again and get a log for you another time.
ROM, magisk 16.6, vanced installer (YouTube), universal dm-verity (ROM has built-in gapps)
Got sent back to TWRP and hit reboot to system one more time for science, and got sent back to TWRP again.
Flashed dm-verity v2 and it booted fine.
OnePlus 5t
DEVILOPS 007 said:
Format data everytime or just once for this to work or format because of treble or what? I'm curious as to when formatting is required and why exactly.
Click to expand...
Click to collapse
I believe he's just telling dude how to decrypt for the first time.
Sent from my OnePlus5T using XDA Labs
bdwilk said:
I'll do it again and get a log for you another time.
ROM, magisk 16.6, vanced installer (YouTube), universal dm-verity (ROM has built-in gapps)
Got sent back to TWRP and hit reboot to system one more time for science, and got sent back to TWRP again.
Flashed dm-verity v2 and it booted fine.
OnePlus 5t
I believe he's just telling dude how to decrypt for the first time.
Click to expand...
Click to collapse
Oh I thought he was responding to you. My bad lol
DEVILOPS 007 said:
Oh I thought he was responding to you. My bad lol
Click to expand...
Click to collapse
Ya, you just need to format data to decrypt
Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Click to expand...
Click to collapse
This is a copypaste from Samsuyng Tab A thread:
repey6 said:
Hi. You can to try Universal DM-Verity and ForceEncrypt Disabler by Zackptg5 from this thred https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
blaz3gamingHD said:
Does this work?
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
I've tested it and it doesn't work, still encrypted.
Click to expand...
Click to collapse
repey6 said:
This is a copypaste from Samsuyng Tab A thread:
Click to expand...
Click to collapse
Of course he's still encrypted this zip isn't going to decrypt your phone. It's for once your decrypted and flashing a rom it will not allow the rom zip to encrypt your device and will allow it to boot decrypted and without the insecure verity check blocking boot.
Sent from my ONEPLUS A5010 using 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"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei P10.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei P10
Contributors
OldDroid, XePeleato, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-27
do you know anyway in which i could unlock my bootloader?
JohnnyMwanza said:
do you know anyway in which i could unlock my bootloader?
Click to expand...
Click to collapse
DC Unlocker is the only way to go as Huawei stopped releasing bootloader unlock codes since July 22, 2018.
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
McEyes said:
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
Click to expand...
Click to collapse
Its a know glitch, just reboot and try again.
netmaniack said:
Its a know glitch, just reboot and try again.
Click to expand...
Click to collapse
I tried rebooting about 10 times and he always did the same.
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
McEyes said:
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
Click to expand...
Click to collapse
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
ej8989 said:
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
Click to expand...
Click to collapse
True, I've read the disclaimer, but if someone, like me, used to install ROMs with the same warning without any problem (like an AOSP rom on my previous phone, which I installed having the TWRP), maybe he/she would think that there is not so much to worry about.
However, I noticed that there isn't a real "guide" on internet about a workaround of the "Just a sec" problem, so I wrote that message also for who needs a help and does not know about the partition check.
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
McEyes said:
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
Click to expand...
Click to collapse
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
doktor29 said:
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
Click to expand...
Click to collapse
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
McEyes said:
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
Click to expand...
Click to collapse
can you link magisk version?
i try many official but i get info "unable to detect boot image"
doktor29 said:
can you link magisk version?
i try many official but i get info "unable to detect boot image"
Click to expand...
Click to collapse
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
McEyes said:
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
Click to expand...
Click to collapse
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
any chance to get rid of this annoying notification of SDCARD after reboot ?
rom ressurection remix
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
so how i can flash magisk without twrp ?
for me it works only data partition is not vivible due to encryption
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
doktor29 said:
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
Click to expand...
Click to collapse
Are you on stock kernel? Does this happen ALL the time or just random?
doktor29 said:
so how i can flash magisk without twrp ?
Click to expand...
Click to collapse
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
ej8989 said:
Are you on stock kernel? Does this happen ALL the time or just random?
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
Click to expand...
Click to collapse
it happen to me every reboot :/
i have only magisk with stock recovery, from instruction above
doktor29 said:
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Click to expand...
Click to collapse
I use the FromFutureRom version that is in the thread I linked before. I think is made especially for Huawei P10/P10+
My data partition is still encrypted.
In order to decrypt data you should format the so called "user data", which is the combination of /data and /sdcard. Don't have to say that you will lose everything on your internal archive, so be sure to backup everything. The external SD card will NOT be affected.
In the TWRP you can to this on the menu "format" -> "format data" -> write "yes" and format everything.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
You are absolutely right, but I said that you can install TWRP or any custom rom AFTER the Treble Rom installation. I am now on Resurrection Remix Treble rom, with a TWRP recovery installed after the rom flash and everything is fine since the first boot.
So today with some testers i managed to make root on OnePlus 8, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator).
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
TIPS:
You can get the stock boot images from the fastboot rom: Fastboot ROMs
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images:
https://androidfilehost.com/?w=files&flid=308379
or
https://sourceforge.net/projects/fastbootroms/files/OnePlus 8/Patched-Stock-Boot/
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
the link to the patched/stock images seems to be wrong
i found this link while going through ur files
https://androidfilehost.com/?w=files&flid=308379
hjjiang said:
the link to the patched/stock images seems to be wrong
i found this link while going through ur files
https://androidfilehost.com/?w=files&flid=308379
Click to expand...
Click to collapse
Yes thanks for the report, i linked the folder before the root folder. However updated the link in the first post
just wondering, is there a way to patch it urself?
It's with locked bootloader or unlocked bootloader ?
i reckon the only way to flash a boot image is to have an unlocked bootloader
Does it work with any OS version?
Is anybody able to upload a 10.5.3-EUROPE magisk patched (and stock) boot image?
If you're on this, DO NOT try with 10.5.2. It involves the SIMs not being usable and the system UI to regularly crash.
I followed this thinking I was on International 15.5.3 so flashed 10.5.3-GLOBAL-magisk_patched. I now cannot connect to WIFI and can't update via local system update as I'm on the latest EU version.
Any suggestions?
Used the unbrick tool to revert back to EU 10.5.1 back to complete stock and locked bootloader. WIFI working.
Ran the same sets again this time using the matching 10.5.1-EUROPE-magisk_patched file and still ran into the no WIFI issue :/
Deano1889 said:
I followed this thinking I was on International 15.5.3 so flashed 10.5.3-GLOBAL-magisk_patched. I now cannot connect to WIFI and can't update via local system update as I'm on the latest EU version.
Any suggestions?
Click to expand...
Click to collapse
flash the stock boot.img
Sent from my IN2015 using Tapatalk
so i updated to 10.5.4 b4 rooting, do i have to wait for a patched.img?
hjjiang said:
so i updated to 10.5.4 b4 rooting, do i have to wait for a patched.img?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-81aPg5T53vlSAwGJWiOPMaW_LZ4r6Bg/view?usp=drivesdk
for oneplus 8 global version
Sent from my IN2015 using Tapatalk
I lost the finger print.
now i can't set up the finger print, not sure if it is because of the root or something else.
anybody having same issue?
I'm running on oos 10.5.4 rooted
{
"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 IN2015 using Tapatalk
Ibramj12 said:
flash the stock boot.img
Sent from my IN2015 using Tapatalk
Click to expand...
Click to collapse
I tried that too but still got no WIFI
Ibramj12 said:
https://drive.google.com/file/d/1-81aPg5T53vlSAwGJWiOPMaW_LZ4r6Bg/view?usp=drivesdk
for oneplus 8 global version
Sent from my IN2015 using Tapatalk
Click to expand...
Click to collapse
thanks ill try this
EDIT: seems to work on my global fone xD
Deano1889 said:
I tried that too but still got no WIFI
Click to expand...
Click to collapse
make sure you are using the correct version.
10.5.3.IN21AA
10.5.3.IN21BA
10.5.3.IN21DA
or you can directly download the latest update.
https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
rename it to "update.zip"
the go
settings >system update >local update
select the update.zip, reboot
re-root if required
Sent from my IN2015 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
QUOTE=Ibramj12;82422497]Guys please help me.
I need the persist partition image
here is how you get it.
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit
Sent from my IN2015 using Tapatalk
also FYI, their doesn't exist a magisk props for in2015, seems like in2013 is the only fingerprint for the time being
Ibramj12 said:
make sure you are using the correct version.
10.5.3.IN21AA
10.5.3.IN21BA
10.5.3.IN21DA
or you can directly download the latest update.
https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
rename it to "update.zip"
the go
settings >system update >local update
select the update.zip, reboot
re-root if required
Sent from my IN2015 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
QUOTE=Ibramj12;82422497]Guys please help me.
I need the persist partition image
here is how you get it.
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit
Sent from my IN2015 using Tapatalk
Click to expand...
Click to collapse
anyone can help me with partition image. the fingerprint isn't working
Sent from my IN2015 using Tapatalk
CTS profile is false for me, how can i fix this? i tried reflashing the boot image and magisk