Database Users

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash

Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).

ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess

I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)

Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.

Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?

Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!

Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck

I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.

ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore

Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.

dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work

Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.

Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)

dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread

Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt

Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

{Guide} How to Root ONEPLUS 3T (Unlock bootloader, TWRP Recovery, SuperSu)

Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting.
1. Download the ADB For Windows from here :-
https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
2. TWRP: https://mega.nz/#!v9MmGQ5C!i5VroRopCVz2_Uoc6Mi2U6N4oDa0HK1SxCrkDrc4mwQ
3. SuperSu: https://mega.nz/#!eh13yLiC!3tkx_RkLg-D8T6mi35zDUB8AYEPLliBsL8yO1dmZbI8
Steps:
1.Backup Data
2.Unlock boot loader
3.Flash Recovery
4.Flash SuperSU
ENJOY
Video:
https://youtu.be/wwd31NU7VC0
Rooting OOS 4.0.3 ONEPLUS 3T
https://youtu.be/0QYp5tkBaao

Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Simply flash the full ROM.zip manually in recovery, typically 1.4GB.
That means not installing the incremental mini zips. And not installing from the settings menu.
It's up to you whether you want to wipe data or cache.

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Download complete zip file n flash using two.

Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
yes if u follow the steps you wont have DM verity issuse.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
Dm verity zip is not needed when you flash SuperSu.

*winces* Ooh, all the files on file hosts? Why not just link to the legit sites?

Very easy to download the required files. Very simple step-by-step video guide. A+
Thanks for putting this together you made my night!

Thanks, I have unlocked bootloader, Installed TWRP, and Super Su.
one question though, when after setting my account going for nandroid backup there I found SYSTEM as well SYSTEM IMAGE.
what is difference between them, What thing should I backup.
Also there is showing your system is Unmounted, so when I should have to mount it.
Thanks to all Once again.

Hello guys, thanks for the guide!
I was wondering if anyone has faced the same problem as me - while trying to root the Oneplus 3T I constantly get a bootloop after flashing SuperSU. The latest TWRP (3.0.4.0) is installed without any problems in fastboot, the system is mounted as r/w, and I don't see any problems during flashing SuperSU package...
I've tried it before and after OOS 4.0.2, I've tried old and new, stable and beta versions of SuperSU, but either way the phone is stuck on bootscreen after flashing.
P. S. If I flash the official ROM after that - it boots up instantly without any errors... And with no root :/

I'm having the same problem

respectableafrican said:
I'm having the same problem
Click to expand...
Click to collapse
So nice to know I'm not alone!
Did you find a way to root your phone?

Try this SuperSU

I heard only SuperSU SR3 works

Just tried both versions (2.79 and the SR3 beta) - unfortunately, the same bootloop happens.

I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help

nishant.roy24 said:
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
Click to expand...
Click to collapse
Power off and boot instead of selecting reboot from twrp

hrsa said:
So nice to know I'm not alone!
Did you find a way to root your phone?
Click to expand...
Click to collapse
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)

respectableafrican said:
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
Click to expand...
Click to collapse
Oh, finally - thank you so much!
Followed the guide on reddit page, and got the Magisk root, with Android Pay compatibility!
I wonder why it was so hard to find

Magisk on Oreo

I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.

I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...

GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?

+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)

+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?

kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!

+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?

GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.

kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)

I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.

kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?

GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:

Do I have to flash no verity?

I really just want to root stock. I have the Boost Mobile Perry.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).

I really don't care about encryption.

guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.

Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.

guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.

Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img

i have the moto e4 mkt which no verity version do i have to flash ?

Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.

madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome

Trying to understand what I broke. Corrupted /data

I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.

j1tters said:
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
Click to expand...
Click to collapse
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...

levone1 said:
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
Click to expand...
Click to collapse
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.

j1tters said:
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
Click to expand...
Click to collapse
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

levone1 said:
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?

j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.

levone1 said:
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
Click to expand...
Click to collapse
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.

j1tters said:
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
Click to expand...
Click to collapse
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.

levone1 said:
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
Click to expand...
Click to collapse
Ohhh. right. I thought you meant recovery didn't do anything with aosp. Read that wrong, brain fart.

So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..

j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
Just wanted to say thanks. Magisk and viper are installed and working. TWRP still errors out with not being able to read /data but I got viper and root, and thats all I wanted.
Thanks!

j1tters said:
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
Click to expand...
Click to collapse
Yeah, I guess still no custom kernels for O yet, so... Did you already try decrypt data with twrp?

Nope. I got what I wanted at this point. I'm leaving well enough alone. I don't see having to really do anything with TWRP in the near future. I'll miss being able to do a full backup, and I'm a little annoyed I cant restore my 7.1 backup but I can live with that. I see I can decrypt but I'm a little gun shy and don't want to break anything again.
At the end of the day AOSP + viper is really all I needed.
Thanks again for all the help.