I rooted my G960F/DS today, and after the rooting procedure, the phone started freezing pretty much every time it enters AOD....
I've searched and found a bunch of ppl having this issue with the G965F.
You could try the newest official beta 16.6 which works as root for me.
The SaftyNet-Test says successful but ctsProfile as well as basicIntegrity say false. It doesn't bother me.
Related
Hello,
I was facing some of the problems everyone is reporting here about random restarts and bootloops even (and mostly) using stock firmwares. As many of you started to have the problems after updates my problem started when I tried to root for the first time when SuperSU was not totally working yet. These problems didn't stop even flashing everything to stock (bootloader, modem, firmware, csc) and other stock firmwares from other countries so I was thinking that my phone was faulty too.
Every reboot my phone asked me for a password that I never set, so there was nothing to put there and I always had to reboot into recovery and flash the "no-verity" script or else I would get stuck in a bootloop or the phone asking me for a decrypt password (that didn't exist).
Sometimes when the phone randomly restarted gave me the "verity encryption" error at the beginning when using the stock recovery, if using TWRP it asked me for a password after semi loading Android (since it didn't found the official recovery to show that error from it), so I always suspected that the Samsung encryption was causing all my problems. Tried everything and even made a post about it (http://forum.xda-developers.com/note-7/help/random-restarts-password-doesnt-exists-t3450678)
So I kept waiting for something that disabled the phone encryption to verify that this was the real cause of this random behaviour before going to Samsung for warranty. Finally @Tkkg1994 came up with the Hydrakernel that disables the encryption so after trying it and formating everything MY PROBLEMS ARE TOTALLY GONE.
My suspects were finally confirmed..... The Samsung encryption was causing all these sh1ty problems (at least in my phone).
So everyone that is flashing stock firmwares even going back to old ones, it seems that doing this doesn't fix anything once you got into this problem for the first time, only disabling the encryption solves it. So my recommendation would be to disable the force encryption from Samsung by using the Hydrakernel and testing again (http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433)
I would like to thank all the devs that are doing their best effort to give us a free Note 7 to enjoy. @Tkkg1994 @dr.ketan @Chainfire it is very admirable that common people like them can solve things that not even Samsung has figured them out yet.
PS: Have you guys flashed this ROM and kernel instead of stock firmwares and continue to have problems with your Note 7??? Give your feedback!!!
Interesting, keep us posted with your phone status...
nice job keeping on testing & we waiting your next result
Hello everyone.
A few days ago i was just normally using my Xperia Z5 Premium then all of a sudden my phone started lagging. No button was responding, screen became totally unresponsive as well. I had to hard shutdown the phone and restart it. It worked but then after about an hour it started to happen again. I just flashed the latest 32.4.a.1.54 firmware (clean install) and started all over again. It worked for a day or two and then back to the same ****ty lag. I am unable to figure out what exactly is the problem. At first i thought that maybe the ta_po+Magisk 14.5 is causing the problem. To clear the doubt i tried to use old drm fix from tobias's tool but it is also happening after it. I have flashed my phone over 10 times to solve the issue by trying to know if a magisk module is causing the problem or not but nothing. I cannot find any error in magisk log nor did this happen on installing any thing. It all started out of nowhere and now i'm pissed. Please someone help me troubleshoot this issue.
I am using stock rom stock kernel for modifications and not the available custom kernels or roms.
P.S: while doing all that drm + root thing i have always followed the exact instructions in doing so. My method worked well with the past firmwares. It also worked with this latest S.H.I.T but now it's bothering me. I have tried searching the web and tried using the available solutions (So called Movie Creator app problem and Blah Blah Blah) but S.H.I.T happended.....:crying::crying::crying:
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Merky_21 said:
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Click to expand...
Click to collapse
You want help without logs? This is a developers site not Magic kingdom!
Im new to this and im not shure if this is the right place to post this please tell me if its the wrong place
I recently rooted my a8 with magisk, everything worked and I have twrp installed too (DM verity and forceencrypt are both disabled)
I now decided to download zANTI the instalation worked and I read that I would need Busybox for these kind of programs so I installed the Magisk Busybox module and restarted.
The problem is when I start the zANTI app, after a few minutes my phone suddenly goes black and then restarts, this also happens if I try to use the scan funktion, it goes up to 7% and even finds a few host but then when it sais starting nmap it restarts again after a few seconds.
Any help or tips would be appreciated!
Thanks
So far ive tried Zanti 3.19-1, Zanti 3.19, Zanti 3.18
None worked
Hey guys,
My Pixel 2XL initially had some reboot issues so I decided to root it, and was able to do that successfully with magisk on stock firmware with some modules installed as well. It regained its functionality for the most part but unfortunately the Wifi stopped working (kept searching, could'nt find any network). It would sometimes randomly work on some reboots but whenever it did, the phone would auto-reboot after a while and lose the function again (but would work perfectly otherwise).
So I decided to unroot and factory reset with stock firmware thinking it might be a partition defect, just to see if that fixes it but it didn't. And what's more, the phone has once again returned to bootlooping like before root. Can anyone help me find out the issue here? And if I can manage to root it again and get it working, is there some way to resolve this issue (maybe through a custom kernel)?