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.
Related
Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.
Hi
After my last updates installing NOS and McAOSP separately
(now I am in Mcaosp ROM Oreo)
the phone goes into randomly reboots and keeps bootlooping once or two times after simple tasks such as playing a game or opening an app e.g root explorer
.but not all the time maybe now maybe after two days really unexpected.
Any fix?
I did factory reset
Wiped data's e.t.c
Restore
Nothing fix the my issue.
Update rom to newest version. try with custom kernals like "agni" or "radon" and magisk to root.
I am in last update. Also tried Agni latest.Magisk fan too. But no luck.
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?
About This Rom
This is a debloated stock rom based on stock F800K_30H. Most likely the last update the V20 will get.
Installation Procedure for F800 L/K/S
Download the F800***.7z to a PC and extract with 7-zip app on Windows PC or the equivalent on OSX / Linux . This will expand to a single 6GB system.img file. Copy over to internal storage on your device.
Update TRWP recovery to 3.4.x.x using TWRP.
Download also the F800 boot imgage and F800K-ezv2020.zip kernel.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Boot into twrp and flash the system image.
Install>Install_Image(bottom right)>navigate to system.img file and select system image partition.
Repeat the same procedure for the boot.img, flash on boot partition.
Flash ezV2020 Kernel and then Magisk. Done.
If you are coming from Oreo download also the Pie partitions and flash that first, then as above. Also wipe data so have your apps backed up.
In the case your were already on PIE no need to wipe data but do wipe Dalvik / ART cache and Cache in TWRP before reboot. Device will be slow for a while and will speed up as Dalvik cache is rebuilt in the background. Sometimes that can take a while especially if you don't let the device rest.
==========================================================
Update Nov 2022: You now need to flash in twrp this Chrome update to pass initial setup screen after phone reset or fresh flash.
F800 - Google Drive
drive.google.com
Release v2
This is based on K rather than L for no good reason (new: flash the K partitions in my repo and ezv2020 K kernel), but makes no difference as all carrier apps have been deleted. This is a 'start again' version rather than an update to ver 1 and is recommended to update due to reports of better performance.
Added
QLens
V30 and G6 themes ( I like the black one with dark grey accents)
Sim unlock app (I think it's for phones locked to sim, not sure if it is or if it works)
Wap Push Service (for carrier settings sent via text msg)
Collage Wallpapers from G6 - only works on Lock Screen, dunno why, i'll try fix.
LG Smart World. You must hide it in Magisk first, then software update. Don't know how to change Korean language, sorry.
If you don't care for any of these additions delete them from /system/product/app , using a root browser
RCT (root check tool) remover has already been applied.
Known issues (minor)
Touch screen is not responsive after coming out of Laf Download Mode at times. To recover this simply reboot into recovery and reboot. It's not that serious and doesn't occur after a normal reboot. You just need to be aware of the fix in case you experience it.
If you have any apn issues do the 'reset apn settings to default' in the apn settings menu. Cuz my carrier apn didn't show up initially.
==========================================================
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
TarAntonio said:
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
Click to expand...
Click to collapse
Install Mixploer from here http://mixplorer.com/
Download the attachment provided and extract the folder to Internal Storage
Using Mixplorer copy and paste the Folder named LGCalendarProvider to...
root>system>product>priv-app
(you may be asked to grant root permission here)
Make sure you can see the LGCalendarProvider Folder is in priv-app folder, now reboot.
Google calendar is working for me now.
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
TheRoyalDuke said:
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
Click to expand...
Click to collapse
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
ezzony said:
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
Click to expand...
Click to collapse
Bluetooth works fantanstic. Connected my portable speaker and it played smoothly, never disconnected.
TheRoyalDuke said:
Edit: F800L30H_Partitions is needed to get fingerprint working.
Click to expand...
Click to collapse
Thanks for that. It might be just the modem that is needed. Can you get into download mode after flashing the partitions? Be careful. That is why I said in the OP don't flash Pie Partitions on non-F800 although you may not have seen that as I added it later.
I have a zip somewhere to flash back oreo partitions. I'll upload it later.
edit: just checked my us996, fingerprint is working fine without flashing pie partitions. Please delete your edit as I don't want anyone flashing pie partitions on non-f800 devices because of the laf download problem.
I will have to figure out what exactly is going on but until then I don't support of advise anyone to flash Pie partitions on any non-F800 device.
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
TheRoyalDuke said:
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
Click to expand...
Click to collapse
Ah good. Because there was an issue with the new Pie LG LAF (download mode) not being detected in LGUP. Experienced that myself. The danger is then if you accidentally deleted TWRP or somehow got corrupted there would be no way to ever flash the phone again and you'd be stuck with what you have. That is why I'm being extra cautions.
Note:
I still don't advise anyone to flash pie partitions on non-f800. There are so many variants it's not certain or knowable if all will be okay for all of them.
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloated right?
xxseva44 said:
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloat right?
Click to expand...
Click to collapse
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
ezzony said:
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
Click to expand...
Click to collapse
Ahh okay, thx for letting me know
Edit: So i flashed it and at first it was very stable but then it crashed to that green apps watchdog bark, i then rebooted and it crashed and showed the purple secure watchdog bite screen a couple of seconds after unlocking the phone. not sure if this is relevant but when it crashed it was downloading about 40 apps, and i was trying to log into instagram. Maybe it was just a fluke, i'll see if it happens again
Edit2: So i rebooted and everything seems fine again
Edit3: okay so it crahsed again, same thing happened, it crashed to the green watchdog bark screen although this time it went from that screen to the purple watchdog bite screen without rebooting or anything. When it crashed, i went to unlock it and it froze while i was unlocking the phone
Could this have anything to do with the fact that my phone was originally a vs995? Cuz i converted it to a us996, I noticed that there was a vs995 pie kernel, should i flash that and see if the crashes stop? I'm not too sure if it would do anything especially since i was running alpha omega oreo with your us996 oreo kernel just fine but it's worth a shot but just to be sure, for now i'll reflash the us996 kernel again and see if the crashes return
update: It worked fine for the past hour but crashed to the watchdog bite screen again, i'll try flashing the vs995 pie kernel and see if the crashes stop. Okay so i successfully flashed it, now i just have to wait and see
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
xxseva44 said:
Ahh okay, thx for letting me know
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Click to expand...
Click to collapse
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
ezzony said:
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
Click to expand...
Click to collapse
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
TheRoyalDuke said:
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
Click to expand...
Click to collapse
You could try flashing the modem only. The pie modem, in twrp. I'd be curious to know what would happen. I have just uploaded it. Worth a try. The fingerprint for some reason uses files in the modem partition. Why there are there I don't know.
Be advised everyone all this mixing and matching pie with oreo may result in unforeseeable negatives. We can only know what works by trial and error. And, your welcome!
xxseva44 said:
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
Click to expand...
Click to collapse
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
ezzony said:
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
Click to expand...
Click to collapse
Yea i double checked, i flashed the us996 pie kernel twice actually, but had the same results
Okay so before i added anything, i tried to open the alexa app again, this time it worked fine and didn't cause my phone to crash, so this time i'm going to open a lot of apps and see if that will trigger the crash
Edit: nope, that did not cause it to crash either, i have no idea what's causing the crashes, maybe it has something to do with the cache because i remember when i tried rebooting after the second crash, it was stuck at the boot animation, it only rebooted after i cleared delvik and cache. Maybe the cache is getting corrupted after a while?
Update: Phone has been running fine for 1 day
Update2: Phone crashed this morning while scrolling to instagram, these crashes seem to be happening at random. Only thing the crashes have in common is that it would happen roughly every 20 hours to a day. Sometimes if i'm unlucky it just repeatedly crashes after a couple of reboots
Update3: Okay yea theres something funny going on with the cache because, i went to the gallery to look at some videos that i know would play but when i tried to play them it kept saying something went wrong, tried a reboot but still the same result. and when i'd watch videos on instagram they looked corrupted, tried force stopping and clearing the cache but still the same result. reboot didn't help either, only thing that fixed those issues was clearing the cache and delvik in twrp
Update: So i have found a temporary solution which is to clear the cache and delvik every once in a while
Idk if this is relevant but what did you come from before flashing this cuz i came from oreo so idk if that could have anything to do with the issue
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.