Database Users

[Q] Nexus 4.2.1 UPDATE failed with Clockwork mod

Can you please help me answer how to install OTA updated with CWM installed. I get this error saying the installation aborted .. it boots into CWM
is there any step by step method to get the new update on nexus 4
Thanks

you need stock rom, no modifications made, and stock kernel for it to work

Download and extract the original 4.2 and fastboot flash system system.img and it'll restore all missing apps.. I had to do it earlier to allow the system to install the update
Sent from my Nexus 4 using xda app-developers app

I reflashed stock recovery but now the update isn't available. Any ideas?

billybennett said:
I reflashed stock recovery but now the update isn't available. Any ideas?
Click to expand...
Click to collapse
update manually.

So I got my update but it keeps failing during install. I'm rooted and every time the update starts it kicks over to CWM recovery and stops with a message something like, "do you want to install this untrusted zip file" I say yes but it still fails. I have even tried to manually install the update through CWM but that fails too. My N7 is rooted but otherwise stock, I have not removed any stock apps or flashed roms or kernels so WTF must I do???

Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham

zelendel said:
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
Click to expand...
Click to collapse
I don't know where, but I saw a few posts about working updates to 4.2.1 with CWM recovery.
However, I'm not getting it to work.
How do I get rid of the recovery without loosing the root?

If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.

You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham

4.2.1 update getting installation aborted
Hey, can some please post the stock Nexus 4 v4.2 build.prop file? I can't seem to install the v4.2.1 update without it...
Thanks...

zelendel said:
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
Click to expand...
Click to collapse
Successfully installed OTA here while rooted with CWM recovery, though everything else is stock.

billybennett said:
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
Click to expand...
Click to collapse
Hey,
got an Error over here with stock recovery and root.
However, tengen says he made it with CWM and root - maybe it's because I'm using stuff like Busybox or the Pimp my Rom APK?
EDIT: I think its because of the %-BatteryMod I'm using. I'll try to flash the custom rom.
Greetings

[Q] ROM HELP for nexus 7

I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!

hettige677 said:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
Click to expand...
Click to collapse
Hello there!
What about a little search? is a search bar in every part of the forum!!!
Anyway there you go:
http://forum.xda-developers.com/showthread.php?t=1745781
Just don't get used to it :good:
Read the forum rules!

So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app

n/m

hettige677 said:
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.

Leonhan said:
That's because you are using a custom recovery.
Click to expand...
Click to collapse
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.
The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).
Leonhan said:
You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Click to expand...
Click to collapse
Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.
The OP should just
- make a full nandroid backup of what they have now
- download the factory 4.2.2 images from Google
- extract the system.img file and boot.img images
( hint for windoze users: 7-zip understands .tgz files)
fastboot flash boot boot.img
fastboot flash system system.img
- reflash a basic SuperSU or Superuser root kit
Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.
If they don't like the result, they can simply restore their nandroid backup.

Question on vendor img and flashing.

I was wondering if anyone has an answer. I got my 6p yesterday and used skipsofts nrk to unlock and root the 6p. All fine and i am still getting the beginning splash screen saying device corrupt. I was reading in the purenexus rom thread and it said to flash the mdb08m vendor img. When I rooted I was and still am on Mdb08l. Am I able to flash that vendor img on the L or do I need to go up to M? Also is there a link or something on how to flash a vendor img and also where I would find it?
Sent from my Nexus 6P using Tapatalk

jeff5347 said:
I was wondering if anyone has an answer. I got my 6p yesterday and used skipsofts nrk to unlock and root the 6p. All fine and i am still getting the beginning splash screen saying device corrupt. I was reading in the purenexus rom thread and it said to flash the mdb08m vendor img. When I rooted I was and still am on Mdb08l. Am I able to flash that vendor img on the L or do I need to go up to M? Also is there a link or something on how to flash a vendor img and also where I would find it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey! Thanks for posting! I would like to know this as well.

The corrupt device message is because you need to completely wipe everything (factory reset including wiping user data). The vendor mismatch error is different.
Sent from my Nexus 6P using XDA Free mobile app

akellar said:
The corrupt device message is because you need to completely wipe everything (factory reset including wiping user data). The vendor mismatch error is different.
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Pretty certain he means the message that says "cannot check device FOR corruption..."

ohlin5 said:
Pretty certain he means the message that says "cannot check device FOR corruption..."
Click to expand...
Click to collapse
That message is apparently part of the bootloader and cannot be removed. At least nobody has found a way yet. It isn't indicating an issue either though, just that the bootloader is unlocked.
Edit: just realized I can't read and that has nothing to do with the original question. You flash the vendor image in fastboot with the command "fastboot flash vendor vendor.img" The vendor image version needs to match the build you are running.
Sent from my Nexus 6P using XDA Free mobile app

I flashed via fastboot last night the m vendor IMG. I had already dl'd purenexus which is on m and gapps. Flashed the vendor in FB then went to recovery and wipe everything minus internal storage then flashed PN and gapps. All is working great just that initial corrupt screen appears. So as of now there's no way to get rid of it?
Sent from my Nexus 6P using Tapatalk

jeff5347 said:
I flashed via fastboot last night the m vendor IMG. I had already dl'd purenexus which is on m and gapps. Flashed the vendor in FB then went to recovery and wipe everything minus internal storage then flashed PN and gapps. All is working great just that initial corrupt screen appears. So as of now there's no way to get rid of it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Correct
Sent from my Nexus 6P using XDA Free mobile app

I have a Nexus 6 (shamu) and to get rid of that message, you need a custom kernel that has the "dm verity" removed. Does this not apply for the 6P? Just throwing this bit if info out there.

H4X0R46 said:
I have a Nexus 6 (shamu) and to get rid of that message, you need a custom kernel that has the "dm verity" removed. Does this not apply for the 6P? Just throwing this bit if info out there.
Click to expand...
Click to collapse
on the 6p it's coded inside the bootloader.

Abaddon said:
on the 6p it's coded inside the bootloader.
Click to expand...
Click to collapse
WOW! Thanks! That's something!

I'm struggling to understand how to change vendor into my nexus 6P due to the fact that I have now NDE63X vendore but I'm not able to replace with nothing different. I mean that I was trying to flash Benzo rom that needs NBD90X but I was not able to flash it though TWRP neither FB, now I would try Resurrection Remix but it's the same....the build no I have at the end of the flashing is still NDE63X.
I'm going crazy with this, I'm felling a dude (as I am) but can someone explain what is missing in my understanding?

akellar said:
That message is apparently part of the bootloader and cannot be removed. At least nobody has found a way yet. It isn't indicating an issue either though, just that the bootloader is unlocked.
Edit: just realized I can't read and that has nothing to do with the original question. You flash the vendor image in fastboot with the command "fastboot flash vendor vendor.img" The vendor image version needs to match the build you are running.
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
The corruption message is just a badge of honor [emoji3]
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
mickjmickj said:
I'm struggling to understand how to change vendor into my nexus 6P due to the fact that I have now NDE63X vendore but I'm not able to replace with nothing different. I mean that I was trying to flash Benzo rom that needs NBD90X but I was not able to flash it though TWRP neither FB, now I would try Resurrection Remix but it's the same....the build no I have at the end of the flashing is still NDE63X.
I'm going crazy with this, I'm felling a dude (as I am) but can someone explain what is missing in my understanding?
Click to expand...
Click to collapse
When you download the correct vendor image you need can use twrp to do it. When your in twrp and St the install screen it's on the bottom right of the screen I believe it says "flash image". Lmk if this helps
Sent from my Pixel XL using XDA-Developers mobile app

bigmatt503 said:
The corruption message is just a badge of honor [emoji3]
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
When you download the correct vendor image you need can use twrp to do it. When your in twrp and St the install screen it's on the bottom right of the screen I believe it says "flash image". Lmk if this helps
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
You realize you quoted a post from over a year ago, right?

Mickjmickj asked his question 1 day ago. What was the point of your post? The guy asked a question YESTERDAY and I tried to help. So yes, the original post was a year old.
Sent from my Pixel XL using XDA-Developers mobile app

akellar said:
You realize you quoted a post from over a year ago, right?
Click to expand...
Click to collapse
It seems someone reply as well

bigmatt503 said:
The corruption message is just a badge of honor [emoji3]
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
When you download the correct vendor image you need can use twrp to do it. When your in twrp and St the install screen it's on the bottom right of the screen I believe it says "flash image". Lmk if this helps
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
I did in that way and furthermore with fastboot but I'm still with the same vendor.
Now I'm with Resurrection Remix using NDE63X
All seems running fine but I've not learned anything new.

vendor image when and why
Okay new to 6p here is my question if i flash say purenexus and my vendor is prior to n4f226i and i flash purenex. do i need to flash the vendor to match that build
i know how to flash it i however did try just that after i did in recovery i got a /vendor dose not exist and had to reflash to factory and start over again ahh
i got it now nevermind

kentek said:
Okay new to 6p here is my question if i flash say purenexus and my vendor is prior to n4f226i and i flash purenex. do i need to flash the vendor to match that build
i know how to flash it i however did try just that after i did in recovery i got a /vendor dose not exist and had to reflash to factory and start over again ahh
i got it now nevermind
Click to expand...
Click to collapse
For anyone in the future that finds this thread, answer lies below:
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning indicates a mismatched vendor and system partition. The vendor partition was integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS build and monthly security update. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line. These will always match up with the factory image of the same Android build (six digit numerical/alphabetical name) for this device.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. If you are a custom rom user, make sure that you flash the vendor.img for the Google monthly security update that you are moving to. Be aware that sometimes AOSP roms utilize the AOSP master branch that has a newer Android build than the monthly security update for this device. You will still need to install that month's vendor.img.
The phone will fail to boot if you mismatch the vendor.img with a different Android version. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat. The vendor.img is typically not included in the custom rom zip but is often available as a separate download.
Click to expand...
Click to collapse

kentek said:
Okay new to 6p here is my question if i flash say purenexus and my vendor is prior to n4f226i and i flash purenex. do i need to flash the vendor to match that build
i know how to flash it i however did try just that after i did in recovery i got a /vendor dose not exist and had to reflash to factory and start over again ahh
i got it now nevermind
Click to expand...
Click to collapse
You flashed the vendor image in recovery? Did you choose the correct partition to flash it to? I've flashed the vendor multiple times in TWRP but never got an error message like the one you are describing. Where did you get your vendor image from?

jhs39 said:
You flashed the vendor image in recovery? Did you choose the correct partition to flash it to? I've flashed the vendor multiple times in TWRP but never got an error message like the one you are describing. Where did you get your vendor image from?
Click to expand...
Click to collapse
wrong vendor image user screw up I got it runs great now with ex kernel substrate thank you for the reply

Can't flash twrp?

Hello guys, I tried to flash Dirty Unicorns ROM
I have a brand new nexus 6p
At first I went through this tutorial:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
First stuck was when I tried fastboot devices in cmd, those USB drivers from sdk manager didn't seem to work, so I downloaded some other driver, which seemed to work
Now I am stuck here:
How To Install A Custom Recovery On Your Device
fastboot flash recovery <filename>.img
So in my CMD I did this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16932 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.827s
and after fastboot reboot, the device is still the same, still the same bootloader, when I hit "recovery mode", there is just the green android robot lying on his back with red ! and after a while the device just starts like normal
also when I start I see "your device software cant be checked for corruption. Please lock the bootloader......" etc and Google logo with unlocked lock in the bottom, but I guess it's normal
any advice please?

solved, /thread

bejek said:
solved, /thread
Click to expand...
Click to collapse
Please post how you solved your issue so it's here for someone searching for an answer in future.

well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...

bejek said:
well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...
Click to expand...
Click to collapse
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?

Heisenberg said:
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?
Click to expand...
Click to collapse
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...

bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?

Jammol said:
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?
Click to expand...
Click to collapse
Ofc I did.
I am not sure where did I see it for the first time, but this step was definitely in more guides than just this one.
for example here:
https://devs-lab.com/root-install-twrp-in-nexus-6p.html
and this is the step I am talking about:
Prerequisites:
Unlocked Nexus 6P bootloader.
ADB USB Drivers
Minimal ADB Package
TWRP Recovery: Nexus 6P.
SuperSU (For Root): Download.
Modified Boot.img: Download.
Installing TWRP Recovery in Nexus 6P:
1. Launch command.bat file & type:
fastboot flash boot boot.img

bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?

Heisenberg said:
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?
Click to expand...
Click to collapse
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F

bejek said:
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F
Click to expand...
Click to collapse
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.

Instead try out,
fastboot boot twrp_src_name.img
(Where twrp_src_name is your TWRP file name)
That should directly boot you to the TWRP. Else try custom TWRP builds like the one with MultiROM.

Heisenberg said:
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.
Click to expand...
Click to collapse
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.

bejek said:
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.
Click to expand...
Click to collapse
If you don't boot into recovery right after flashing it, the standard recovery will overwrite it. If you want to prevent this, after flashing TWRP, boot directly into TWRP. Flash latest SU to root it (This will prevent the system from overwriting twrp on reboot.)

supersu - maybe these make bootloop?

Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks

I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk

funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk

so...i'm in 8.1 and these is the conclusion in that state after few tests.

I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk

What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk

stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.

the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..