Develop Bugs

Infinite Bootloop

Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.

Make sure you are wiping data, cache and dalvik.
Make sure you didn't get a bad download on the rom you are trying to flash.

I am running stock kernels and have never installed any non stock kernels as stock seems to run just fine. I have wiped everything completely and I've tried two different roms and get the same problem. I don't think it has to do with it being bad downloads. Thank you for the advice though guys. Anyone else have any input? I may just have to go to the verizon store and see if I can exchange it out.

Dude. I had that too some weeks ago and had the problem that I encrypted the phone, which made me not getting into recovery mode. I downloaded a fresh restorer rom from samsung. After everything was fresh I never saw the failure again.
Sent from my Galaxy Nexus using XDA App

murflee33 said:
Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.
Click to expand...
Click to collapse
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/

Geezer Squid said:
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Click to expand...
Click to collapse
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.

zephiK said:
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.
Click to expand...
Click to collapse
Not kidding. That link to tells him how to return to stock and re-lock the bootloader.

HELP!!

So I flashed my phone back to stock. Accepted the OTA for 5.1.1. Today I took my phone off of my charger it went into a boot loop for some reason and wont come out. factory data reset and cache clear don't help. Samsung rep at best buy doesn't have 0g5 yet to flash. Does anyone know how to get a hold of the ODIN files to reflash my phone. THANK YOU VERY MUCH!!!

sherkinator19 said:
So I flashed my phone back to stock. Accepted the OTA for 5.1.1. Today I took my phone off of my charger it went into a boot loop for some reason and wont come out. factory data reset and cache clear don't help. Samsung rep at best buy doesn't have 0g5 yet to flash. Does anyone know how to get a hold of the ODIN files to reflash my phone. THANK YOU VERY MUCH!!!
Click to expand...
Click to collapse
No Tar available at the moment...
http://forum.xda-developers.com/note-4-sprint/general/help-stuck-bootloop-og5-t3172299
---------- Post added 08-05-2015 at 12:19 AM ---------- Previous post was 08-04-2015 at 11:54 PM ----------
Can you confirm that youre back up and running?

xxSTARBUCKSxx said:
No Tar available at the moment...
http://forum.xda-developers.com/note-4-sprint/general/help-stuck-bootloop-og5-t3172299
---------- Post added 08-05-2015 at 12:19 AM ---------- Previous post was 08-04-2015 at 11:54 PM ----------
Can you confirm that youre back up and running?
Click to expand...
Click to collapse
Not really sure whats going on over on that thread. So let me give you my comprehension of it. So my phone cannot be rooted with 5.1.1. So my question becomes how do I flash TWRP? Also, if I can enable TWRP can I flash CM 12.1? I am not up and running quite yet.
Thanks

So I tried fixing this beast at 2 am when I got home lol everything was a blur and I really was tired from work so nothing made sense. I just reread the thread and tried it. CM 12.1 IS UP AND RUNNING>>>>THANK YOU ALL SOO MUCH!!!

Looking for Odin flashable NE4(correction:NJ1) for D2ATT

I am looking for the stock 4.4.2 NE4 rom for D2ATT to flash through Odin.
A little background. Phone soft boots on me, and I am able to get into recovery. However, if I try to flash anything or restore a backup, the phone reboots. I am able to get into download mode, but can't find the correct stock file to flash. I have the recovery flashable file, but can't flash it. Every where I have searched for the Odin file has been a dead end.
This has happened to me before, and Odin did the trick. That was on 4.1.1 though which was before the bootloader changes.
Anyone have the Odin file by chance? Thanks.
[CORRECTION]: I am on the NJ1 bootloader/modem.

There is no stock firmware available for later builds.
What were you trying to do when you got to the soft brick?
Any errors when you try to flash a rom?
What roms have you tried flashing?
What is your current bootloader version?
Sent from my SGH-T999 using Tapatalk

I was afraid of that. Actually I wasn't doing anything (this time lol). I was running the official CM nightlies (I think I flashed last week some time, coming from Pac Rom).
When I try to flash in recovery, the screen goes black several second into flashing and then reboots into a boot loop. If I try to turn on it is a boot loop as well. I am in the latest NE4 modem/bootloader version.
Edit: I was able to do a wipe in recovery before reboot. It had an error with data during the wipe. I wasn't able to get a picture in time so I don't know what the exact error was.
Edit #2: When trying to flash I get the error "cannot mount system" before it boot loops on me.

Ok so you were running cm and are trying to get back stock correct?
If I recall correctly, you need to just flash the stock recovery and factory reset from there.
You can find the stock recovery in one of enewman17's bootloader/modem threads. Let me know if you can't find it.
Not sure that'll solve it for you, but I'd say it's worth a shot.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 01:33 AM ---------- Previous post was at 01:28 AM ----------
NE4 stock recovery.
https://www.androidfilehost.com/?fid=23681161096070493
Flash from custom recovery.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
NE4 stock recovery.
https://www.androidfilehost.com/?fid=23681161096070493
Flash from custom recovery.
Sent from my SGH-T999 using Tapatalk

Thanks! Ok question for you. How will this get the stock firmware installed? I still have the problem of no Odin flashable firmware.
Edit: It looks like I am unable to get into recovery at this point. Phone just reboots.

Is it possible the phone has a problem with the power button? Was it hyper-sensitive before the bootloops started?

audit13 said:
Is it possible the phone has a problem with the power button? Was it hyper-sensitive before the bootloops started?
Click to expand...
Click to collapse
That's possible. I had this issue before though, and it was fixed when I use Odin to reflash stock. Right now it's at the point where it will automatically try to boot up when I put the battery in.
Edit: The other thing I was thinking of, was possibly corrupted partitions, or perhaps the storage is corrupted/ needs formatted.
Edit#2: Just did some back reading, and realized I am on the NJ1 bootloader, which is the latest 4.4.2. I thoroughly regret upgrading, so if you are reading this and considering an update, DON'T DO IT!!!! I will update the OP and thread title accordingly.

The phone now will not stay booted in download mode either. Ends up rebooting after a couple of seconds.
I think this one is pretty much hosed, as even if I were able to unbrick it, there still is the matter of no compatible software that can be flashed. It is not my daily driver, so not the end of the world, but it still sucks. The biggest loss is several videos I took this weekend of a martial arts tournament my son was in.
Thanks so much guys for your help on this. It is much appreciated.

Sounds like you've got the faulty power button. If it tries to turn on when you insert the battery, it's a sure sign of this.
Replacements are pretty cheap if you care to try soldering it yourself. Otherwise most repair shops should be equipped to help you out.
The reason I suggested factory resetting from stock recovery is because many people have had similar issues when coming from cm. Not sure why, but it does a better job at reformatting the internal memory. After doing the reset, most people are able to boot into stock again.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 03:13 AM ---------- Previous post was at 03:04 AM ----------
Oh, and it is possible for corruption to occur when it is constantly rebooting. I don't think it's common though. I had one that was doing exactly the same thing for over a month and I never had any data loss or corruption.
It's only a temp fix, but try blowing into the power switch with a can of compressed air. You can also try giving it a swift, gentle (but hard) tap on the edge of a wood table. (Try on both sides of the phone and around the button itself). This is how I was able to keep using mine until I got around to fixing it. Beware though, hitting it too hard, or against something with no give can easily crack the glass! Obvious, I know, but figured I should mention it anyway!
Oh and if you get it to come back on, don't even breathe on the power button! It'll be super sensitive still. I couldn't even use my case until it was fixed.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Sounds like you've got the faulty power button. If it tries to turn on when you insert the battery, it's a sure sign of this.
Replacements are pretty cheap if you care to try soldering it yourself. Otherwise most repair shops should be equipped to help you out.
The reason I suggested factory resetting from stock recovery is because many people have had similar issues when coming from cm. Not sure why, but it does a better job at reformatting the internal memory. After doing the reset, most people are able to boot into stock again.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 03:13 AM ---------- Previous post was at 03:04 AM ----------
Oh, and it is possible for corruption to occur when it is constantly rebooting. I don't think it's common though. I had one that was doing exactly the same thing for over a month and I never had any data loss or corruption.
It's only a temp fix, but try blowing into the power switch with a can of compressed air. You can also try giving it a swift, gentle (but hard) tap on the edge of a wood table. (Try on both sides of the phone and around the button itself). This is how I was able to keep using mine until I got around to fixing it. Beware though, hitting it too hard, or against something with no give can easily crack the glass! Obvious, I know, but figured I should mention it anyway!
Oh and if you get it to come back on, don't even breathe on the power button! It'll be super sensitive still. I couldn't even use my case until it was fixed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. I will give that a shot.

Stuck in bootloader

So yesterday I was taking a look to xda developers when I saw a post with cyanogen mod 14 for the Nexus 5x so I installed it. Everything went ok but after looking at the OS for a bit I thought that the OS i had was better (it was nougat 7.1.1, beta program) so before installing cyanogen mod i had made a backup of my older system. I tried to restore the backup but when i tried to turn on the phone it froze when booting, and that started happening over and over, it turns on shows google logo starts booting and freezes, turn of, turns on ....
I've tried to install many diferrent roms from here xda, the normal ones in root toolkit and nothing works, every rom freezes when booting. I've wiped the phone i've done everything i could do in TWRP.
Please if someone out there can help i would be very thankful.
Im sorry for bad english!

Usually you repair it by flashing firmware

rp158 said:
Usually you repair it by flashing firmware
Click to expand...
Click to collapse
How can i do that?

mike_seventeen said:
How can i do that?
Click to expand...
Click to collapse
Since you already tried toolkit and it didn't work,? Wugfresh?
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
mike_seventeen said:
How can i do that?
Click to expand...
Click to collapse
Read this carefully, at the end there is a tutorial how to flash stock. It's number 9 or 10. http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930/page150

Stevica Smederevac said:
Since you already tried toolkit and it didn't work,? Wugfresh?
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
Read this carefully, at the end there is a tutorial how to flash stock. It's number 9 or 10. http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930/page150
Click to expand...
Click to collapse
Sorry I had to leave. but i done what said in the tutorial and everything went ok. Now i have to install a rom right?
Thanks!

mike_seventeen said:
Sorry I had to leave. but i done what said in the tutorial and everything went ok. Now i have to install a rom right?
Thanks!
Click to expand...
Click to collapse
Yes but be careful what version of Nougat it is and try to match the vendor accordingly.

Stevica Smederevac said:
Yes but be careful what version of Nougat it is and try to match the vendor accordingly.
Click to expand...
Click to collapse
I installed the lastest version from google's developers website and now it just stays in google logo forever when booting

mike_seventeen said:
I installed the lastest version from google's developers website and now it just stays in google logo forever when booting
Click to expand...
Click to collapse
Didn't you say that everything went ok? What did you do in the meantime? You just flashed stock img? Try to do a factory reset from stock recovery

Stevica Smederevac said:
Didn't you say that everything went ok? What did you do in the meantime? You just flashed stock img? Try to do a factory reset from stock recovery
Click to expand...
Click to collapse
I done step 10 as you said to do from that post (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930) then i installed the rom and know its basically happening the same thing that happened in first place.
I probably done something wrong installing the rom.
I've done factory resets several times in stock and custom recoverys

mike_seventeen said:
I done step 10 as you said to do from that post (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930) then i installed the rom and know its basically happening the same thing that happened in first place.
I probably done something wrong installing the rom.
Click to expand...
Click to collapse
Or it's a hardware issue. Apparently, a lot of 5x are dying suddenly and lately. Try the factory reset first before you flash stock again.

Stevica Smederevac said:
Or it's a hardware issue. Apparently, a lot of 5x are dying suddenly and lately. Try the factory reset first before you flash stock again.
Click to expand...
Click to collapse
I'll do as you say, but if i can´t solve this i'm kinda screwed because i have no possibilities to buy another phone and i have this one for like 3 months, i have to solve this, i really do. Thanks for all the help! Really appreciated.

Ran into the same exact problem as OP, while restoring 7.1.1 backup when coming from MIUI 8 rom.
Same stuff when completely restoring to stock/installing a different rom etc.
Mike, did you restore EFS from TWRP backup? I have a feeling that it gets corrupted and it wont let the device boot anymore.
Because TWRP runs absolutely fine and even the file manager in it works perfectly, which indicates that it may not be similar to the hardware issue which people might be having.
Phone restarts after first loop of the bootscreen (after all the blue-red-yellow-green dots have turned to their initial size), correct?
Edit: See post #14 for fix.

tauio111 said:
Ran into the same exact problem as OP, while restoring 7.1.1 backup when coming from MIUI 8 rom.
Same stuff when completely restoring to stock/installing a different rom etc.
Mike, did you restore EFS from TWRP backup? I have a feeling that it gets corrupted and it wont let the device boot anymore.
Because TWRP runs absolutely fine and even the file manager in it works perfectly, which indicates that it may not be similar to the hardware issue which people might be having.
Phone restarts after first loop of the bootscreen (after all the blue-red-yellow-green dots have turned to their initial size), correct?
Anyway I did not manage to get it to boot again, I recommend you restore to stock via fastboot and lock your bootloader before you take it to warranty.
Click to expand...
Click to collapse
I restored through TWRP the backup i have then when i turned it on the dots just stoped the animation then the phone restarted and it just kept restarting over and over again. The problem is that the warranty ended few months ago, so or i solve this problem or i lose my money.
(I only have the phone for about 3/4 months but the warranty was almost over when i bought it(online))

mike_seventeen said:
I restored through TWRP the backup i have then when i turned it on the dots just stoped the animation then the phone restarted and it just kept restarting over and over again. The problem is that the warranty ended few months ago, so or i solve this problem or i lose my money.
(I only have the phone for about 3/4 months but the warranty was almost over when i bought it(online))
Click to expand...
Click to collapse
It seems you made the same mistake as I - You backed up the EFS partition and restored it. I read that this function does not work correctly with TWRP 3.0.2-1,2,3. It will corrupt your EFS partition.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Follow the first post exactly (even though its from the 6P thread), and it will get fixed .

tauio111 said:
It seems you made the same mistake as I - You backed up the EFS partition and restored it. I read that this function does not work correctly with TWRP 3.0.2-1,2,3. It will corrupt your EFS partition.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Follow the first post exactly (even though its from the 6P thread), and it will get fixed .
Click to expand...
Click to collapse
You have no ideia of what you've done, you are an angel, you just SAVED my life, i done as it says in the thread and the phone started, I can´t explain how thankful i'm feeling right now, THANK YOU SO MUCH, really, thank you so so so so much, I will never NEVER forget you. Thank you for saving my life! :victory: :good:

mike_seventeen said:
You have no ideia of what you've done, you are an angel, you just SAVED my life, i done as it says in the thread and the phone started, I cant explain how thankful i'm feeling right now, THANK YOU SO MUCH, really, thank you so so so so much, I will never NEVER forget you. Thank you for saving my life! :victory: :good:
Click to expand...
Click to collapse
No problem, just share the link to the thread from the 6P forums if you find someone with a similar problem.

Wrong Pin - Issue

Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?

thenags said:
Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?
Click to expand...
Click to collapse
Rooted or not? If rooted, what magisk version are you using?

Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk

thenags said:
Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832

No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I had this issue by rooting with the non-twrp method. I believe it also was caused by not removing all security before rooting...fingerprints and all. Eventually I ended up in the bootloop of death which I recovered only with fastboot flash-all.
I rooted again after all this (needed my substratum) and so far no issues since remembering to disable all security before rooting.

Ya know. I've always removed all security before flashing but read it's no longer necessary and when flashing Pie it was the first time I ever didn't. Wonder if that's related.
Sent from my Pixel 2 XL using Tapatalk

thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk

Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you. At the gym right now but will give it a shot when I'm home.
Sent from my Pixel 2 XL using Tapatalk

Does it solve the PIN Incorrect issue in TWRP as well?

JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users

Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Just installed it. Hopefully this does it. Thanks for the help :good:

After a sequence of
1 Shutting down the phone
2 rebooting into safe mode
3 shutting down the phone again
and finaly my pin will work.
I believe its something with android P as I had the updated versions of Magisk and TWRP and worked fine on O.
And of course googles solution is to reset everything. That dose not help ever. Only makes me more frustrated.

Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !

Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
WorldOfJohnboy said:
Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !
Click to expand...
Click to collapse
Scary as **** the first time, eh? I had just got into bed for the night and was ready to sleep and rebooted my phone for some reason. Bam. Wrong PIN. I was like here we go... gonna be a long night.

praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?

JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Badger50 said:
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users
Click to expand...
Click to collapse
Try "adb reboot recovery" next time or switch to a custom kernel. This way you should always be able to enter your pin without the freezing/crashing. I'd recommend flashing @nathanchance's Flash Kernel via Franco Kernel Manager. Just flash and forget.

SirVilhelm said:
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?
Click to expand...
Click to collapse
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change

praveen6585 said:
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change
Click to expand...
Click to collapse
Boot loop on this one as well. oh well, the stable version doesnt seem to be having issues for me.