After rooting my s9+ with the modified Magisk, my phone sometimes becomes unresponsive. I cannot identify any sort of trigger for this to happen, it just does. The AOD displays but does not update. The notification LED still blinks, but when I go to unlock the phone it freezes and I am forced to soft reset it. I am root with Magisk and have TWRP installed. I followed Max Lee's tutorial on how to root the S9+. Any ideas on why this is happening and how to fix it?
Hey, Did you have any luck with this, i am having the exact same issue?
having the same problem i followed Max Lee video and everything work fine until the phone started freezing
same issue on the G960F/DS....
wonder who can help us regarding with this issue.
For everyone having this freezing after rooting...attention to detail is absolute paramount, go back and re-read the twrp thread by jesec. For those (possibly those having freezing issues) who find that challenging, here is a snippet of jesec exact words..." Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection".
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
To reiterate...flash a custom kernel before root or be SCREWED
I'm not saying this is 100% u guys issue, but seems kinda likely?
can someone post links or steps on how to fix this freezing lock screen issue, i tried reading the threads but did not find anything, thanks
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
crs_dev said:
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
Click to expand...
Click to collapse
Can we flash this Elementalx over the N965F_Root_for_OEM_issue_devices/Magisk we already installed ?
I already installed the TWRP, No-verity opt encrypt and the N965F_Root_for_OEM_issue_devices package on my friend's 960F.
I would be really greatful if anyone could help me with this.
I had the same issue after having troubles initially getting Lineage flashed and working on my S9.
I removed Magisk, reset and it still was freezing after a lock.
I reflashed Lineage through TWRP and now all seems to be back to normal with no freeze after lock.
Possibly try the steps I did and see if they worked out for you.
hey guys, you solved the issue?
i experience same Problem..
Any one notice , this issue occurs after we apply lock screen password or biometric security. in my device i notice, when i apply lockscreen password or biometric lock my phone freeze. after i remove all lock and set default to swipe...its not freezing. anyone sees that
I solved the same issue (1 hour ago, so I hope it's fixed now) installing first:
ElementalX Kernel
and than installing:
G965_Root_for_OEM_issue_devices_V5 (the lastest available right now)
Following the instruction on the XDA Thread
Hope this can be helpfull to solve it
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
KevAngelo14 said:
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
Click to expand...
Click to collapse
What is the different in Soldie between Patched Kernel and ELS custom kernel?
Related
I have a Galaxy S2 I9100 which I had flashed to CF-Root XX_NEE_LPD-v5.5-CWM5. After this I flashed CM9 and have tried CM10 - all have been working fine without problems,
Recently, wanted to try MIUI and tried flashing it. Everything works *except* the lock screen. Simply put, it doesn't lock. Tried setting to other locking methods and nothing works. Bascially, when the screen is off and when you wake it, it just starts (kind of like the No Security setting). I need to mention that before before I flash to CM9, the lock screen also did not work on the stock rom which had been updated by Samsung service center when I sent the phone in for servicing(which is why I rooted and flashed CM9 as the phone was out of warranty anyways).
I came across info that someone had a similar problem and resolved it by using Siyah. Flashed Siyah 4.15 using ODIN and still not working. And the strange thing is Siyah does not seem to be in. I can get into Siyah the first round but if I boot into recovery again I seem to end up in CF-Root (no fancy Siyah eye logo). Did I screw up something here?
I reviewed the MIUI tutorial and it recommended doing things like replacing bootloaders, etc using ODIN (en.miui.com/a-123.html). Having not done this before(except using ODIN to get CF-Root), I'm apprehensive to try it.
I'm running out of ideas to try. Any tips and suggestions here would be useful. Thanks.
tanchankai said:
I have a Galaxy S2 I9100 which I had flashed to CF-Root XX_NEE_LPD-v5.5-CWM5. After this I flashed CM9 and have tried CM10 - all have been working fine without problems,
Recently, wanted to try MIUI and tried flashing it. Everything works *except* the lock screen. Simply put, it doesn't lock. Tried setting to other locking methods and nothing works. Bascially, when the screen is off and when you wake it, it just starts (kind of like the No Security setting). I need to mention that before before I flash to CM9, the lock screen also did not work on the stock rom which had been updated by Samsung service center when I sent the phone in for servicing(which is why I rooted and flashed CM9 as the phone was out of warranty anyways).
I came across info that someone had a similar problem and resolved it by using Siyah. Flashed Siyah 4.15 using ODIN and still not working. And the strange thing is Siyah does not seem to be in. I can get into Siyah the first round but if I boot into recovery again I seem to end up in CF-Root (no fancy Siyah eye logo). Did I screw up something here?
I reviewed the MIUI tutorial and it recommended doing things like replacing bootloaders, etc using ODIN (en.miui.com/a-123.html). Having not done this before(except using ODIN to get CF-Root), I'm apprehensive to try it.
I'm running out of ideas to try. Any tips and suggestions here would be useful. Thanks.
Click to expand...
Click to collapse
Check the link below, hope it will be of some help to u
http://forum.xda-developers.com/showpost.php?p=23641669&postcount=8
Sun90 said:
Check the link below, hope it will be of some help to u
http://forum.xda-developers.com/showpost.php?p=23641669&postcount=8
Click to expand...
Click to collapse
Thanks for the link. Tried the solution but no joy - screen not locking like it should.
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button
The gestures randomly stop working after the marshmallow update. So, I clean flashed 3.1.3 with stock recovery after deleting cache and data. Gestures randomly stop after sometime but works again if you reboot. Any way out?
Now, I am rooted with twrp recovery.
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
I think that explains it.
Exodusche said:
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
Click to expand...
Click to collapse
Thanks I will do my research!
pavikum said:
Thanks I will do my research!
Click to expand...
Click to collapse
No problem also meant to say gestures never worked better. . Almost to good every time I clean my screen flashlight or music starts playing lol.
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
vinz_uk80 said:
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
Click to expand...
Click to collapse
Haha, at least I have some company now!. Thanks, that trick works!
maybe we followed the similar steps to arrive at this issue.
I was on Sultan CM rom 13 , when the 3.1.1 update arrived, I unrooted my phone locked the OEM and clean installed 3.1.1 through stock rcovery after clearing data and cache. My phone gesture problem started from here, I updated to 3.1.2 through OTA and that did not solve it, so I clean installed 3.1.2 and later 3.1.3. Rooted it with modified superSU and blu spark twrp recovery. Did you follow the same steps.
I am not wiping the internal storage yet, as suggested by 'Exodusche', as I am doing my research to understand the potential risks. But, I did not really find any helpful article till now.
Hello Axon 7 XDA Users,
as you know, more and more users have a stupid reboot bug. Unfortunately no DEV found the time to take a look into the logs I and other users posted on the forums.
THE BUG
Soft reboots and boot loops at least once a day
- while charging
- while watching videos or surfing
- even then turned off (Ghost booting)
SOFTWARE AND DEVICES
Reports on nearly all custom roms based on LOS
All A2017 / 2017 U / 2017 G models
WORKING SOLUTIONS
A
I seem to have fixed the problem and want to ask you to try my method:
The problem is probably caused by Magisk, all versions from 13.5 till 14.5x beta
After switching to LineageOS integrated root method I am reboot-free since 3 days of intense usage.
Tutorial to uninstall magisk:
- Download magisk-uninstaller and LOS root addon on LOS ROMs (Downloads are attached)
- Reboot into recovery
- Install magisk uninstaller zip file
- Reboot into recovery (maybe not necessary)
- Install LOS root addon
- Wipe dalvik and cache.
- Profit :good: and report back
B
Only use magisk v14 or try 15.2
THX @notese
C
Try disabling Magisk hide
THY @digiNZM
I don't use magisk and I still have reboots. Reboots occur about once or twice a week.
Pastinakel said:
I don't use magisk and I still have reboots. Reboots occur about once or twice a week.
Click to expand...
Click to collapse
Thank you for your feedback.
Maybe you should post what setup you have and which apps you are using with root / xposed access or mods.
I had the reboot issue with the latest lineage os and magisk on b25 universal bootstack.
Currently using Dark ROM with magisk on b32 bootstack for the past week or so and no reboots.
A2017U
SilentEYE said:
Thank you for your feedback.
Maybe you should post what setup you have and which apps you are using with root / xposed access or mods.
Click to expand...
Click to collapse
My setup is pretty plain vanilla, no mods. I have the lineage root installed, but it's disabled most of the time.
If I remove Magisk and go with Lineage root, will I lose Safetynet? I need Android Pay to work.
I had the problem with random soft reboots for quite a few months. There would be no similarities between when the reboots happened, for example it would occur whilst watching YouTube videos, browsing Google Maps or even just leaving the phone in sleep mode. Someone on XDA suggested switching from Magisk v14.5 Beta to stable Magisk v14.0, and since then I haven't had a problem.
Advising people to ditch Magisk altogether might not be the best advice, as for me just switching back to the stable version worked. Remember there have been beta versions of Magisk v14.0 for months and it was definately affecting v14.3 as well as v14.5.
That's weird.
I'm using magisk myelf for a long time and never had reboot issues. :/
Only when using incompatible modules or bad settings.
Maybe that's where the real issue is.
P. S.
I'm using latest stable magisk on latest stable RR for a while no and I get zero reboots.
P650SE said:
I had the problem with random soft reboots for quite a few months. There would be no similarities between when the reboots happened, for example it would occur whilst watching YouTube videos, browsing Google Maps or even just leaving the phone in sleep mode. Someone on XDA suggested switching from Magisk v14.5 Beta to stable Magisk v14.0, and since then I haven't had a problem.
Advising people to ditch Magisk altogether might not be the best advice, as for me just switching back to the stable version worked. Remember there have been beta versions of Magisk v14.0 for months and it was definately affecting v14.3 as well as v14.5.
Click to expand...
Click to collapse
You probably read my advise. My fav rom is AOSP Ex and it was driving me nuts the whole random reboot thing. Your description of the symptoms are exactly like the ones I was having. At the beginning I though it was an issue with substratum but it kept happening even without having substratum installed.
I tried switching roms (Dark Rom, Lineage, and RR) and all had random reboots. The final epiphany I had was that I was using magisk beta 14.5 on all of them. I didn't install any custom kernel or any other thing beside magisk 14.5 and one module (viper). I tried reading at the logs but couldn't trace them back.
I figured to try AOSPex without root as the only common thing between the roms was magisk. After this, the reboots and crashes stopped (I tested this for a week). I started reading in the magisk forums and found people with the same symptoms as ours. I didn't see any major complain with the stable magisk 14.0.
My current setup is ASOP ex with llama kernel and magisk 14.0. I have had this for about two weeks and no random reboots so far. The only problem I have encountered was that I lost root access once and I had to reboot on my own account to regain root (maybe a module incompatibility, I have installed two additional modules since then). Other than that, all is good.
Final tip: I only turn on the magiskhide setting when I need it for a specific app. I have it off by default. I don't want an extra process running all the time if I don't need it or use it regularly (can only be a good thing for battery).
Hope this helps
I got the reboots even with magik v14.
Added @notese his solution to OP
I've only got Magisk for a month or so, but reboots began way before that. So I don't Magisk is the culprit.
hboa said:
I've only got Magisk for a month or so, but reboots began way before that. So I don't Magisk is the culprit.
Click to expand...
Click to collapse
What root method did you use before?
Which rom?
Which root apps?
If you provide us some more, maybe we can hit the sweet spot of the bug.
To all :
Write at the end of your comment your settings
Device
ROM
Kernel
Modem
Root method
Root apps
Had Reboots with Magisk v14.x in different ROMs (Vertex, AICP, AOSP) and with different Kernels. Since i disabled Magisk-Hide it stopped (past 3 weeks). Maybe a weird coincidence. Just thougt i share this. Maybe someone can try too?
Current: AICP (unofficial), LLAMA non-EAS Kernel, Magisk latest (v14.5), MicroG.
digiNZM said:
Had Reboots with Magisk v14.x in different ROMs (Vertex, AICP, AOSP) and with different Kernels. Since i disabled Magisk-Hide it stopped (past 3 weeks). Maybe a weird coincidence. Just thougt i share this. Maybe someone can try too?
Current: AICP (unofficial), LLAMA non-EAS Kernel, Magisk latest (v14.5), MicroG.
Click to expand...
Click to collapse
I always had magisk hide disabled and had the reboot problems.
I will add your solution to topic
I personally had some reboot and bootloop problems while on AICP and LlamaSweet and I thought it was the rom. However I then went to Dark Rom with LlamaSweet and the reboots happened again. I posted about this and someone mentioned 14.5 might be the problem. I installed 14.0 and for the past week? I haven't had a problem. So for me it seems so far to be 14.5 as well. Also as of right now I have BeastMode kernel running. Has anyone tried 14.6 yet?
I will post screenshot of my superuser and modules pages.
I have the latest beta version of Magisk and I have reboots once or twice a day, but not necessarily all days. I have the stock camera and "Enable AK4490 HIFI DAC" magisk modules.
I had reboots on the latest DarkRom, Magisk many times a day for at least a month and a half. Since hurricane Maria cell service was almost impossible to find. I noticed everytime my phone lost coverage it would reboot.
Changed sim to another carrier with great coverage just a few weeks ago and reboots have since gone away. Hmmm
eaponte23 said:
I had reboots on the latest DarkRom, Magisk many times a day for at least a month and a half. Since hurricane Maria cell service was almost impossible to find. I noticed everytime my phone lost coverage it would reboot.
Changed sim to another carrier with great coverage just a few weeks ago and reboots have since gone away. Hmmm
Click to expand...
Click to collapse
Did it hang in the soft reboot loop?
SilentEYE said:
Did it hang in the soft reboot loop?
Click to expand...
Click to collapse
Nope, it would just reboot everytime I drove thru certain areas. For instance, as soon as I passed my towns high school, boom restart.
If I had 3G then all of a sudden it dropped to zero bars, boom restart.
The only way I would not get the reboots was installing DrakenFXs B32 with Magisk. Or turning on airplane mode when I knew I would go thru an area with no service.
Convinced me LOS based rom had problems with handling towers and low signal. I tried them all same reboots.
@eaponte23
your problem seems to be different and is a combination of modems and your provider. I know that there has been similar problems with CM /LOS based ROMs on other devices, depending on the Service provider. These lead to total signal loss or reboots.
The Magisk problem is cauing constant reboots.
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
satanishere16 said:
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
Click to expand...
Click to collapse
Indeed that's what I tried first because I usually solved boot loops with that method in other phones in the past. But with this one that trick does not work, I tried with several magisk versions before trying other things that didn't work either such as restoring a nandroid backup with TWRP or wiping everything and formatting data on TWRP. The only thing that worked was the method I described in OP, which I found in other thread in this forum. I have read reports about other people suffering the same problems, so I know I'm not alone.
By the way it seems to happen only with stock ROM. Which custom ROM are you using?
Regards
Pixel experience android 12....
Dev tab
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Edit : After about 10 reboots, the phone went back to bootloop.
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Sperafico said:
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Click to expand...
Click to collapse
Thank you very much. Next time I will try switching to magisk canary channel. I'm on stable and sticking to 24.1 because the last time I updated from that version to 24.3 I got into a boot loop.
8vasa8 said:
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Click to expand...
Click to collapse
Thanks for your answer. In my case the first thing I tried was flashing magisk again, then restoring a full nandroid backup with twrp, and then formatting data in twrp, but none of these steps worked.
I also heard about this problem being solved in custom ROMs but I haven't found any that fit my needs or any that has everything working, so I prefer to keep on rooted stock.
#metoo . We need devs to look into this problem. Been using rooted Android phone for years but now it s***s without root on Nord 2.
As long as you use an untouched stock rom (or after modding re-flashed by OnePlus servicepoint, rebooted into stock recovery, wipe all and re-flash stock, in a OnePlus store), root works fine on stock rom. Every attempt different than above will fail one day or another. I decided not to take OTAs because too many things can go wrong / turn unstable.
The phone is my daily driver, also for work. But I am rooted with Magism 24.3 (stable) and have various modules running including LSPosed, Shamiko, USNF, and in LSPosed GravityBox, XprivacyLua pro and a few more.
Works awesomely. Just don't touch things afterwords. In that case, yes, the phone sucks. Big time.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
shoud what can i do any bramhastra or something ?
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
[email protected] said:
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
Click to expand...
Click to collapse
TWRP and custom roms works without issue. Even root is working with custom.
NANDroid does NOT work on stock rom! TWRP does, but no NANDroids possible.
Unfortunately I agree...
I spent so much time because of manipulations that I am used to doing, and which leads to a boot loop and a brick of the phone immediately afterwards.
The only solution I had was to flash the rom, which of course leads to a total reset each time and a considerable waste of time.
This is my 3rd and last OnePlus phone that I buy, I'm sick of all my lost data and hours spent just getting it started.
Oh my oneplus nord 2 is now in final bootloop. Cant make anything work, just keeps rebooting when plugging in power so $350 down the drain. Would not recommend..
Why down the drain? It's not 1 year old, so Oneplus will renew firmware under warrantee.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
U r wrong
I'm not sure if it's just a coincidence, but for me, it always happens after about a week or two of ignoreing "you have an update available" popup. I thought maybe it modified the boot image, like magisk, to run at the next startup.
I agree that this is very annoying. If I didn't need Google Pay, I'd just install another rom.
Like said. Have your device Factory-flashed by OnePlus, REBOOT to stock recovery, do a FULL WIPE and FACTORY FLASH stock AGAIN! Only with the official OnePlus tool and software.
Only this way all your old fiddling around is erased. If you ROOT then, all will be fine. Of course, neglect further updates, but the device will work fine. Mine is in this state, heavily tweaked (Magisk, Zygisk, USNF, GravityBox, etc. etc. and it runs stable for over 10 weeks without any hickup.