Database Info

XCover 3 (SM-G388F) root on 5.1.1

So, I received this phone as an award in a competition, and when I wanted to root it... nope. No root for this phone. Only for 4.4.4, but I hate ****Kat and I don't want it. So, I updated to 5.1.1 and I was looking for root.. didn't find anything. And those "universal" roots such as KingRoot, Kingo Root, TowelRoot didn't work. I also tried installing TWRP, but after installing it and rebooting into it, the phone got stuck on "recovery is not seandroid enforcing". After booting the phone and than entering the recovery, the "recovery is not seandroid enforcing" appeared again, but instead of getting stuck, the stock recovery booted. So I flashed the stock rom with stock recovery just to remove that annoying error via odin.
Any ideas how to root this f*****g knox device?
Thanks

Please..

i have the same probleme. Nothing work for root.

Hi together, i am mucho interested, too.
Also slightly skilled linux user, so if anyone has a clue where to start rooting this thing i can give it a try.

Mhh I also need a way to root this device because I need a full Image of my /data Partition.
My first idea was to flash the Kitkat bootloader and TWRP. However it will not but a L /system.
So we need a custom L system image which has the already installed SuperSU.
I really like to try it but however my task is to restore photos and not to hardbrick this phone.
Can anybody try a custom /sytem image which is Prerooted? Heimdall should be able to flash it.

_Beni_ said:
Mhh I also need a way to root this device because I need a full Image of my /data Partition.
My first idea was to flash the Kitkat bootloader and TWRP. However it will not but a L /system.
So we need a custom L system image which has the already installed SuperSU.
I really like to try it but however my task is to restore photos and not to hardbrick this phone.
Can anybody try a custom /sytem image which is Prerooted? Heimdall should be able to flash it.
Click to expand...
Click to collapse
If you have a clue where to find such images i can try. Without root this phone is useless to me, so i wouldn't mind bricking it

Tried to flash SBOOT, SBOOT2, Loke_Primary, Loke_Recovery ... it is now hard broken
Yeah maybe i forgot it has no Qualcomm processor where you even can flash a image even you dd if=/dev/zero of=/dev/mmc.
Now giving my old OnePlus Two to her.
You need to register at SAMMobile there you can the latest 5.1.1 for xcover3, you need to extract the image with 7zip then unpack the system.img with sparsed, then mount it via loop-back device. Now umount it, repack the image with sparse and flash the result into SYSTEM with heimdall.
Good luck, I ****ed it up

Oh sh*t, sorry to hear dude! Okay, this evening i can give it a try. Am i guessing right that i want to put the SuperSU binary into the /system/app? Or what's the best way to root this?

todomade said:
Oh sh*t, sorry to hear dude! Okay, this evening i can give it a try. Am i guessing right that i want to put the SuperSU binary into the /system/app? Or what's the best way to root this?
Click to expand...
Click to collapse
Yeah, however I'm not sure how su exactly works.
I know took a look at UPDATE-SuperSU.zip.
This lines are interesting:
if ($SAMSUNG); then
# Prevent "KERNEL IS NOT SEANDROID ENFORCING"
SAMSUNG_CHECK=$(cat /sutmp/boot.img | grep SEANDROIDENFORCE)
if [ $? -ne 0 ]; then
echo -n "SEANDROIDENFORCE" >> /sutmp/boot.img
fi
fi
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
Click to expand...
Click to collapse
It seems its just appends SEANDROIDENFORCE at the end of the boot.img and then flashes it.
Maybe it is the same for the recovery.
You could just try to "echo -n "SEANDROIDENFORCE" >> twrp-3.0.2-*.img"
and then flash this image via heimdall.

Okay, looks like i should dig some deeper into that matter. I guess i can try your suggestion within the next week. I'll post an update if i make any progress.

_Beni_ said:
Yeah, however I'm not sure how su exactly works.
I know took a look at UPDATE-SuperSU.zip.
This lines are interesting:
[...]
It seems its just appends SEANDROIDENFORCE at the end of the boot.img and then flashes it.
Maybe it is the same for the recovery.
You could just try to "echo -n "SEANDROIDENFORCE" >> twrp-3.0.2-*.img"
and then flash this image via heimdall.
Click to expand...
Click to collapse
Okay i tried it, sadly no success.
Still getting "Recovery is not Seandroid Enforcing" and default recovery
Will now try to pack a boot.img myself and flash it.
Other approaches or tips are highly appreciated!

Is the "Recovery is not seandroid enforcing" showing up on the most recent build of twrp, 3.0.2.0. For the lollipop build of the device?? I want some confirmation before deciding to flash twrp and then supersu into my phone running lollipop?
Newest twrp link: https://dl.twrp.me/xcover3ltexx/

Matt07211 said:
Is the "Recovery is not seandroid enforcing" showing up on the most recent build of twrp, 3.0.2.0. For the lollipop build of the device??
Click to expand...
Click to collapse
Affirmative.

VolterPL said:
Affirmative.
Click to expand...
Click to collapse
So do you mean that the "recovery is not seandroid enforcing" shows up with the newest twrp build (3.0.2-0) for our device while running lollipop? Are you able to use the twrp recovery and phone as normal even though that message flashes on boot.
I geuss a fix could be compiling the kernel with the flag disabled on the flag that stops you from switching between enforcing and permissive modes. As done on this guide, http://graemehill.ca/compiling-permissive-android-kernel/ . This would allow the recovery to set itself to be running in permissive mode, when it runs "setenforce 0" as seen
https://github.com/TeamWin/android_device_samsung_xcover3ltexx/blob/android-4.4/init.rc
The source code for the Samsung phone, http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=g388f
I am willing to build/compile the kernel, but due to this phone being my main phone, I am not in a position to test it out, would anyone here be willing to try?
The modified kernel will also allow you to run the OS in permissive mode if done through the terminal.

Matt07211 said:
So do you mean that the "recovery is not seandroid enforcing" shows up with the newest twrp build (3.0.2-0) for our device while running lollipop? Are you able to use the twrp recovery and phone as normal even though that message flashes on boot.
Click to expand...
Click to collapse
Yes, I can confirm it's true. The phone works fine. When I try to go to the recovery mode, it shows said message and boots to the stock recovery.

VolterPL said:
Yes, I can confirm it's true. The phone works fine. When I try to go to the recovery mode, it shows said message and boots to the stock recovery.
Click to expand...
Click to collapse
I got a few questions to ask
How are you flashing the twrp image? Is it via odin and are you using the newest twrp build (3.0.2-0)
I am willing to work, read up and compile anything necessary to get the recovery working on the device, but due to it being my only phone I cant afford to mess around with it much, so are you willing to try out stuff for me e.g. flashing a custom kernel with the ability to toggle selinux modes?
I believe a fix for the "recovery is not seandroid enforcing" can be fixed if I recompile the kernel with a flag set to false (It a custom flag from samsung that disallows the changing of selinux modes, "EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=false") allowing for the twrp recovery to change "setenforce 1" to a "0" allowing the recovery to run in permissive mode. http://graemehill.ca/compiling-permissive-android-kernel/ , https://su.chainfire.eu/#selinux , https://source.android.com/security/selinux/
If you are willing to help test for me I would really appreciate it And once I get the recovery working I am gonna root my phone by flashing the SuperSu.zip.

Matt07211 said:
How are you flashing the twrp image? Is it via odin and are you using the newest twrp build (3.0.2-0)
Click to expand...
Click to collapse
Yes, I am using the newest Odin and the newest TWRP, downloaded from TWRP site.
I would like to help you if, and only if, there's absolutely no chance of bricking my phone as I've bought it recently for quite a lot (at least for me). I don't care about warranty, as well as triggering KNOX.

VolterPL said:
I would like to help you if, and only if, there's absolutely no chance of bricking my phone as I've bought it recently for quite a lot (at least for me). I don't care about warranty, as well as triggering KNOX.
Click to expand...
Click to collapse
I can't say that their is not a chance for a brick, but all I am changing is one single flag from "true" to "flase". Their is always a chance at bricking your phone when working with root, tons, custom recovery and kernels as you are messing with the system, but as long as you have either a backup (nandroid) or now how to fix it (flashing stock firmware), their is very little chance of screwing up, and if screwed up you will in almost all cases be able to fix the problem
But yea if the device stuffs up some how e.g. unable to boot you would able to boot your phone into "download mode" and flash stock firmware, although losing you data e.g. apps,. Your phone would be back in a functional state.
Once I am able to get the recovery working properly (booting and running (in permissive mode)) I will root my phone, make a nandroid backup and then I am willing to start adding custom goveners to the kernel and would be willing to share/get help devloping the kernel in the future.
I might be able to provide the kernel later this week (internet limitations are the reason for a long wait) and will post instructions on how to flash the kernel, and how to flash stock firmware (for either you stuffed up and need to fix the phone, or for testing properly with everything at stock and then working the way up, kernel and then twrp)
So if you are willing, i would appreciate the help if given

Matt07211 said:
I can't say that their is not a chance for a brick, but all I am changing is one single flag from "true" to "flase". Their is always a chance at bricking your phone when working with root, tons, custom recovery and kernels as you are messing with the system, but as long as you have either a backup (nandroid) or now how to fix it (flashing stock firmware), their is very little chance of screwing up, and if screwed up you will in almost all cases be able to fix the problem
But yea if the device stuffs up some how e.g. unable to boot you would able to boot your phone into "download mode" and flash stock firmware, although losing you data e.g. apps,. Your phone would be back in a functional state.
Once I am able to get the recovery working properly (booting and running (in permissive mode)) I will root my phone, make a nandroid backup and then I am willing to start adding custom goveners to the kernel and would be willing to share/get help devloping the kernel in the future.
I might be able to provide the kernel later this week (internet limitations are the reason for a long wait) and will post instructions on how to flash the kernel, and how to flash stock firmware (for either you stuffed up and need to fix the phone, or for testing properly with everything at stock and then working the way up, kernel and then twrp)
So if you are willing, i would appreciate the help if given
Click to expand...
Click to collapse
@ Matt07211 If you need a tester. here i am. But what i need is, a step by step for flashing with heimdall on linux mint 18 in easy english. mx phone is sm-g388f with 5.1.1

@VolterPL @yy1
So but this is gonna be an onslaught of questions and information, I would appreciate if you are able to work through this (READ EVERYTHING AT LEAST ONCE) and test/answer my questions.
Some info: When I was searching for info for how to use heimdall for yy1 because I never used it before, I happened to stumble upon a bit of info that I found interesting, and which may solve one of our problems.
In one of the comment sections a user mentioned that their recovery gets replaced each time with stock, a user replied mentioning that their is a script that runs at boot that replaces the recovery if its been tampered with e.g. TWRP, with a stock recovery. So with a bit of digging (ES File Explorer FTW!!) I happened to find the script mentioned in "/system/bin/install-recovery.sh" and the fix is to rename the file, therefore being unable to run at boot and therfore not replacing the custom recovery.
So I believe one (maybe all) of our problems with the recovery being unable to boot can be fixed as follows, would appreciate help/testing here.
Sidenote: I still plan to build a custom kernel, as I would like the ability to run in permissive mode if needed (also including running recovery in permissive mode as well) and adding custom governors as time progress.
Now time for the fix/instructions:
NOTE: I am not responsible for any damage to the phone, system, tripping KNOX, warranty or your insanity
1. Download Odin, I am using version v3.12.3 (sorry yy1, won't have a guide for Haimdell yet as on phone typing this out) and make sure to have ADB, Fastboot and Samsung drivers installed and backup any important files
2. Download newest SuperSu (yep we are gonna try rooting the phone) from this link: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1
and then put it on the root of the phones internal memory
3. Download the newest TWRP image for our device, which should be 3.0.2-0, link: https://dl.twrp.me/xcover3ltexx/ which should be in the .img.tar format
4. Would probably be best to enable USB Debugging and make sure you have everything backed up and have all files downloaded and Samsung drivers working before preceding any further. If you don't then you should fix that.
5. Launch Odin and boot device into download mode (Power, Volume Down and Home buttons at the same time, for a few seconds.), ensure that the phone is connected to the computer USB port
6. Check Odin and make sure the "added" message is displayed; also, the ID:COM field should now be turned yellow or blue â?? if not, reinstall USB drivers and retry the steps from above.
7. Click on the AP button and then load the TWRP recovery file from desktop. Then, make sure Re Partition and Auto Reboot fields are not checked. Make sure especially that the auto reboot is un-ticked, or this wont work properly as the install-recovery.sh would be able to work before we could get into the recovery at least once.
8. Click "Start" and once finished the â??passâ? message will be displayed; also the ID:COM field will be turned green â?? then you should unplug the USB cord and reboot your device into recovery mode (Reboot straight into recovery or you are gonna have to flash it all over again, due to the install-recovery.sh script)
9. Once in recovery, do a nandroid backup and then flash the SuperSu.zip and reboot
10. Verify that you have root and then download and install a file manager that allows you to modify the /system area, I suggest ES File Explorer and then navigate to "/system/bin/install-recovery.sh" and rename the "install-recovery.sh" to "install-recovery.sh.bak". On a side note, according to the TWRP page, if you boot into TWRP at least once it will patch the stock ROM to prevent this happening. So if TWRP has acctually done this then you probably wont need to modify this file, but try rebooting into recovery at least once after booting to the android OS to see if TWRP is their before modifying the file. If TWRP is their then you can skip the last step.
11. Now due to the "install-recovery.sh" script running at the most recent boot, we will have to re-flash the TWRP recovery once more as the current recovery has been reverted back to stock due to the script. So repeat the steps to flash TWRP one more time and verify that the recovery is persistent across reboots etc.
Outcomes:
- Should have a persistent recovery due to the disabling of "install-recovery.sh" script
- Should have Root on the phone
Stuff wanted to be completed in the future:
- IF this has actually worked, I would like feedback once completed the above steps stating if recovery is persistent across boots and can verify root access. If this worked I will write up a separate thread for rooting this phone and see if we can then get a section on XDA for this phone
- Recompiling the kernel to allow the changing of selinux modes between "enforcing" and "permissive", and as time progresses adding more CPU governors. I will be working to develop this myself so any help would be appreciated.
NOTES/Questions:
- Appreciate your input if this is successful
- If it still flashes the "recovery is not seandroid enforcing" and if the recovery still works in spite of that fact
- If you achieved root, please mention this
- Thank you for taking the time to read and test this if you do
- @yy1 I will write a tutorial for using Heimdall depending on this success of rooting and twrp this phone
Sorry for the wall of text and good luck

Installed twrp phone reboots to twrp

I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files

cgrimm9 said:
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
Click to expand...
Click to collapse
Did you fastboot boot into TWRP, then flash twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip? Were you stock prior?

Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal

cgrimm9 said:
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
Click to expand...
Click to collapse
Yes, you are not supposed to install twrp, just boot into it. If you install it by mistake, you go back, flash stock boot.img, and do it again.
This is from Dees_Troy's post located here
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.

@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Tulsadiver said:
Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
Click to expand...
Click to collapse
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...

alienjon said:
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
Click to expand...
Click to collapse
Things have changed with 8.1. you have to root with magisk. From slot b you cannot fastboot flash boot_a boot.img?
I believe the instructions now are to boot to TWRP, install TWRP pixel installer zip, then flash Magisk zip
Here is where TWRP files are here
https://dl.twrp.me/sailfish/

Tulsadiver said:
From slot b you cannot fastboot flash boot_a boot.img?
Click to expand...
Click to collapse
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)

alienjon said:
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
Click to expand...
Click to collapse
Yes, the zip file that is located where the flash-all.bat is. Unzip it and flash the boot.img.
I bought a Pixel 2 on swappa. It had different bootloader's on slot a and slot b. I couldn't flash updates when on slot a. I thought I was hosed but from slot b I could flash to slot a so now I'm fine. Slot a had a preview bootloader.

[guide] how to root zenfone 3 official oreo firmware

HERE IS A STEP BY STEP GUIDE TO ROOT ZENFONE 3 FOR PEOPLE WHO HAVE UNLOCKED THEIR BOOTLOADER AND ROOTED THEIR NOUGAT ROM PREVIOUSLY.
-first of you need to update your firmware to oreo.
-if you have unlocked your phone bootloader and/or rooted, you need to download and flash the latest nougat firmware through stock recovery which is 'WW-14.2020.1712.85' here https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_BIOS/
-after you finished flashing the latest nougat firmware, boot your phone as usual. and then download the official oreo firmware which is 'WW-15.0410.1712.31 here https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_BIOS/
-then put that 'WW-15.0410.1712.31' firmware to your SD card
-your phone will automatically detect an oreo firmware is available to be flashed that are located on your SD card then click on update
-then your phone will go to the updating/flashing process took around 5-10 minutes. after you're done your phone are now using the official stock firmware.
-then to proceed to root your oreo firmware, you need to flash a TWRP recovery. you can download twrp recovery here https://drive.google.com/drive/folders/1KYX8G6wgOa_X7uJfIar7ENuk2Q1nQyWB
-choose the right model for your phone either ZE520KL(5.0inch) or ZE552KL(5.5inch)
-rename the twrp recovery you just downloaded to "oreo_twrp_recovery.img"
-then put your phone to 'fastboot' mode and connect usb to laptop/pc
-put the twrp recovery that you just downloaded inside the 'Kit Root Zenfone 3' on your laptop/pc
-press shift and right click then click on 'Open command window here'
-then on cmd, type "fastboot flash recovery oreo_twrp_recovery.img" and click enter
-it will tell you flashing is finished
-then click on cmd type 'fastboot reboot' and click enter
-then your phone are now using TWRP recovery instead of the stock recovery
-next, go to magisk manager . com (no space)
-download the magisk manager apk version 5.5.5 [2.4mb]
-download magisk v15 [5.81mb] zip file
-boot your phone and install the magisk manager apk like normal
-then put the magisk v15 zip file to your SD card
-then boot your phone to TWRP recovery and flash the magisk v15 zip file
-after done, reboot system from twrp recovery
-open the magisk manager app and you're ROOTED!
done. your welcome.
[MY REVIEW OF THE OFFICIAL OREO FIRMWARE AFTER ALMOST A WEEK OF USE]
-oreo battery life sucks compare to stock nougat rom
-i can notice the battery drain faster than when im on nougat
-system performance, for me 5-10% faster than on nougat, especially the in settings or swiping the notification panel, other than its the same
-gaming performance are 10-15% worse than on nougat. when i play a game called 'Dokdo', moving the ship around the ocean are smoother when im on nougat and the framerate are stable, but when i play the game on oreo, the framerate are lower and i can feel the difference when im playing on nougat and oreo. the game feels more smoother when im on nougat compare to oreo. other games performance also noticeable when i play 'Rules of Survival', i can feel the framerate are slightly smoother on nougat compare to oreo
-there's no bugs that i found so far
[MY FINAL REVIEW OF ZENFONE 3 OFFICIAL OREO FIRMWARE]
-oreo battery life is real ****, i dont even have many apps installed and the battery life is already ****
-i prefer the nougat firmware compare to oreo.
-the only thing that i like about oreo is the quick settings icon are changed, it looks cleaner and smaller compare to nougat the quick settings icons are bigger and doesn't look good
-everyday i check on https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_BIOS/ hoping there's a new oreo firmware update saying 'battery life improved' or something thats all i want
*14 february guide updates*
incase you guys hasn't already know, there's a second(current latest) oreo updates from asus, the firmware is called 'Version WW-15.0410.1801.40'.
if you are on rooted oreo firmware 'Version WW-15.0410.1712.31' and you want to update to the latest oreo version and root it again. follow this steps below:
*NOTE: you can't proceed to flash the stock firmware if you're phone are rooted so you need to unroot or remove magisk root first before flashing the oreo firmware otherwise the flashing process will fail or a possible of bootloop will occur, so follow the steps below carefully*
-first, you need to remove magisk root by downloading the magisk uninstaller zip file from the magisk manager . com (no space) or from their xda page
-then flash/install the magisk uninstaller zip file from TWRP recovery
-after you flashed the uninstaller, you're phone are now unrooted. then you can proceed to flash the 'Version WW-15.0410.1801.40' firmware.
-after you flashed the 'Version WW-15.0410.1801.40' firmware your TWRP recovery will be replaced back to asus stock recovery
-so you need to reinstall TWRP recovery as usual through fastboot
-reboot your phone as usual and as you know your phone root access is currently gone since you uninstalled magisk earlier
-to root your phone back, download and install the latest magisk manager from their site or xda site
-click on download zip file, and put that magisk zip file on your SD CARD
-boot to twrp recovery
-flash the magisk zip file that are located on your SD CARD
-reboot system
-now your latest 'Version WW-15.0410.1801.40' firmware are now rooted again.
YES I KNOW IT IS SUCH A HASSLE, BUT THIS IS WHAT YOU MUST GET THROUGH IF YOU WANT ROOT ACCESS. ANDROID IS NOT EASY.

By the way, don't go to magiskmanager<dot>com. It's not official.
Download Magisk from the official thread here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

w1040 said:
-next, go to magisk manager . com (no space)
Click to expand...
Click to collapse
Careful with that site, as that's not an official distribution site for Magisk. There was a tweet from XDA regarding that site within the past few weeks. The only 100% trustworthy place to get it is from the official thread.
I'm getting better battery life on Oreo than I did on Nougat. I did do a factory reset after installing Oreo, though, so if you haven't done that it's worth a try.
You're right about the framerate issue with some games. Some that ran fine on Nougat get oddly choppy at times on Oreo. The last Oreo beta (although it had the same version number) was a heck of a lot worse than the release version, so hopefully the next update will help.

the reason why i put the magisk manager official site is because i rooted my phone by downloading both the magisk manager apk and the zip file and the app and the zip file from their official site works for rooting my phone so i think there is no harm. if you feel insecure you can just go to https://forum.xda-developers.com/app...mless-t3473445

Not working.
I exactly followed the steps but I could not install twrp. Stock recovery still keeps running.
However, If I use the previous version of twrp (20180203) phone cannot boot, then had to flash roms from M to O.
Edit: I tried over and over again and succeeded at last, but I do not know how exactly!

asenler said:
I exactly followed the steps but I could not install twrp. Stock recovery still keeps running.
However, If I use the previous version of twrp (20180203) phone cannot boot, then had to flash roms from M to O.
Edit: I tried over and over again and succeeded at last, but I do not know how exactly!
Click to expand...
Click to collapse
at cmd when you're phone on fastboot. after you typed "fastboot flash recovery (name of your recovery)".img and enter, make sure it says flashing successful.

new firmware
How about ZE552KL_ WW_15.0410.1801.40 ?

asenler said:
How about ZE552KL_ WW_15.0410.1801.40 ?
Click to expand...
Click to collapse
what about it? i have yet to flash it

So the same procedure applies.
Flash the update + go to fastboot + re-install magisk.
Success.
Thanks everyone.

asenler said:
So the same procedure applies.
Flash the update + go to fastboot + re-install magisk.
Success.
Thanks everyone.
Click to expand...
Click to collapse
yes, its the same procedure. the latest firmware update is still oreo afterall

GUIDE UPDATES - 14 february

Hi !
So yesterday I tried flashing TWRP but no luck.
I'm on the latest firmware (1801), bootloader unlocked, stock recovery with no root.
When I try to flash TWRP with fastboot, I get no error message but I still have the stock recovery instead of TWRP.
I tried multiple times and downloaded the file again but it doesn't work.
Any idea ?

aftee you flashed twrp through fastboot. type on "fastboot reboot" on cmd. then if your phone directs you to stock recovery instead of twrp. click on reboot system in your stock recovery. then it will brings you to twrp. i know its weird. but thats what happen to me too at first.
then if you finally got to twrp and you reboot system from twrp but your phone still brings you back to twrp recovery everytime or it stucks on asus logo (bootloop), dont panic, go to twrp and flash your stock oreo firmware that are located from ur sdcard from twrp, then when you reboot system from twrp, then your phone will boot to normal. dont worry it wont erase data.
try this. it works for me.

Guys. Can I use the above, android already oreo but not in unlock bootloader.

Putra.dim said:
Guys. Can I use the above, android already oreo but not in unlock bootloader.
Click to expand...
Click to collapse
its not possible to root zenfone 3 without unlocking bootloader.

w1040 said:
its not possible to root zenfone 3 without unlocking bootloader.
Click to expand...
Click to collapse
I've been looking for how to unlock zen 3 oroe. but i did not find it. please help me. i want to root my phone.

Here is the official unlock method.
You will not be able to get OTA updates then, but zenfone3 may not get any upgrade anyway.

I found the solution to my problem (couldn't boot into twrp after flashing it)
1-After flashing twrp, do not fastboot reboot !
2-Unplug the device
3-Power it off (long press power key)
4-Power it on into recovery mod (long press power key + low volume key)
You should end up in twrp recovery or on a screen suggesting to boot into recovery which you do
5-A message will appear asking to allow modification of twrp recovery. Swipe to allow.
6-Done !

w1040 said:
aftee you flashed twrp through fastboot. type on "fastboot reboot" on cmd. then if your phone directs you to stock recovery instead of twrp. click on reboot system in your stock recovery. then it will brings you to twrp. i know its weird. but thats what happen to me too at first.
then if you finally got to twrp and you reboot system from twrp but your phone still brings you back to twrp recovery everytime or it stucks on asus logo (bootloop), dont panic, go to twrp and flash your stock oreo firmware that are located from ur sdcard from twrp, then when you reboot system from twrp, then your phone will boot to normal. dont worry it wont erase data.
try this. it works for me.
Click to expand...
Click to collapse
After updating on 15.0410.1801.40, i flash TWRP through fastboot, and i get stuck in bootloop on Asus logo. I go back in TWRP,flash the 15.0410.1801.40 zip, and i remain in bootloop.
With a custom recovery, we didn't need any No Verity File Encrypt like root in Nougat? (On nougat I root my ZE552KL by following this process: https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926)

siberflyers said:
After updating on 15.0410.1801.40, i flash TWRP through fastboot, and i get stuck in bootloop on Asus logo. I go back in TWRP,flash the 15.0410.1801.40 zip, and i remain in bootloop.
With a custom recovery, we didn't need any No Verity File Encrypt like root in Nougat? (On nougat I root my ZE552KL by following this process: https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926)
Click to expand...
Click to collapse
if you got bootloop after trying to reboot ur phone from twrp after flashing twrp. flashing the stock oreo rom from twrp again will make your phone boot. thats how i did it. im not sure why it doesn't work for you.
we still need "no verity..." message in oreo. that no verity message appears are actually caused by your phone bootloader unlocked not because of your phone rooted.

[TWRP] [Port] L.R.-Team recovery OMFG-Mod-From Cactus -to -Umidigi-F1

First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.

hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock

Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.

Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done

New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file

ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?

Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.

Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.

ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.

mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.

ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI

Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).

Stuck in a bootloop, please help

Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]​
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.

Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?

next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.

NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?

You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....

Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.