Related
Good afternoon gents!
This is the first time I post on this forum so I apologize in advance if I am not going to provide all the details regarding my problem. I'll try to be as explicit I can with my issue.
A couple of weeks ago I bought a LG Nexus 5, second hand. After one day of use the device started to randomly reboot. The odd thing is that the reboots seem to be "soft". After the device restarts there is no data loss, even the recent apps are still there. The reboots are as random as I can get, when browsing with Chrome, checking emails, or playing a game.
I tried several fixes, including costum kernels, costum ROMs and so. The problem persisted with the official KitKat 4.4.4 and Lollipop 5.0, 5.0.1 and 5.1.
Currently I am running stock Lollipop 5.1 with stock kernel and TWRP 2.8.5.2 recovery and the device is rooted.
Below I attached a screenshot with the device's current configuration and a text file with the kmsg log from the last reboot.
Faulty power button.
Reboot phone into bootloader/fastboot.
If it random reboots in the bootloader too, it's likely the power button.
Nope, I already tested this. The device reboots during use, either heavy or simply browsing the menu.
Sent from my Nexus 5 using XDA Free mobile app
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Just curious, Are you undervolting?
I don't know exactly what undevolting implies. Could you give me more details please?
vektor1993 said:
I don't know exactly what undevolting implies. Could you give me more details please?
Click to expand...
Click to collapse
Lowering the voltage the CPU runs at, at certain frequencies.
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
vektor1993 said:
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
Click to expand...
Click to collapse
Try posting another log if it happens again.
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
vektor1993 said:
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
Click to expand...
Click to collapse
This log shows a kernel panic.
My n5 reboot today without any reason
That was the only thing I understood from the log too. Do you have any idea what's the reason for these kernel panics and a possible way to fix them?
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
vektor1993 said:
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
Click to expand...
Click to collapse
Same problem as this guy
http://forum.xda-developers.com/showpost.php?p=59551481&postcount=8615
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Good day lads!
I tried since the last post more possible fixes, and the only thing that showed some resuslt was downgrading to 4.4 bu the device still resarts exactly once a day. I am going to switch to another phone.
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Click to expand...
Click to collapse
If you just recieved a new device and you have the possibility to RMA it, I suggest doing it. I went as far as page 30 on google searching possbile fixes and came up with no valid result.
I am currently on rooted OOS stable v 9.0.0 with blu_spark v51 and xXx mod. My OOS camera kept freezing/crashing and I have to force rebooted it everytime. Anyone have encountered this problem? Please advise
Try stock kernel, some reported having issues with cam + custom kernel. No idea why not all is affected.
Yes, I'm having very FREQUENT issues where the entire system freezes and locks up and I have to hard reboot. Happens very often when opening the WhatsApp camera (from the photo button in the text field on any conversation) as well as once in the actual camera app, which I've only opened a couple of times since switching over to the phone. It's infuriating really. This is the kind of bug you expect from poorly-made custom roms, not software that is supposed to be a stable, professional release.
This is on a 6T, though, but the software is very close and I've seen numerous people complaining about the same issues on both devices over on the OnePlus subreddit.
And to clarify, I'm running stock except for having Magisk root. This is a problem in stock OOS that OP needs to address.
Same issue here
9.0.2 Pie on OnePlus 6
Rooted with Magisk 17.2
Camera/phone will freeze close to every time I open it
Restart the device and it will open
Can't seem to find much about it on OnePlus forums except for people saying to reset the cache and then closing the thread off
I'm having the same issues...
Any new solutions?
ult1m4tum said:
Same issue here
9.0.2 Pie on OnePlus 6
Rooted with Magisk 17.2
Camera/phone will freeze close to every time I open it
Restart the device and it will open
Can't seem to find much about it on OnePlus forums except for people saying to reset the cache and then closing the thread off
Click to expand...
Click to collapse
rasluht said:
I'm having the same issues...
Any new solutions?
Click to expand...
Click to collapse
This solution in the 6T forum seems to have worked for me: https://forum.xda-developers.com/showpost.php?p=78138000&postcount=3
Specifically, I uninstalled the camera using magisk debloater then reinstalled the version from apkmirror... so far it all seems fine now.
Is the rom flashed in both a/b partition? Some people have solved these freezing issues by flashing on both a and b because they only flash in one partition not both which caused their cams to freeze. Uninstalling the cam and reinstalling could also help
possible fix
my gcam mod and the stock camera crashed always when i opened them, i'm also on xXx rom with custom kernel.
i have nova launcher and when i flashed xXx again, like to update and have nova launcher in xXx profile activated it causes my camera apps to crash. Disable your launcher and try your cameras. Maybe this helps someone.
i just updated to latest 10.5.7 Global version via OTA, and before rebooting installed magisk to the inactive slot, and then rebooting resulted in bootloop..
restored to previous slot in fastboot and tried the OTA process again, and resulted in bootloop again..
now i have switched back to the old slot running 10.5.6..
anyone knows why the process resulted in bootloop, and any fix for this?
tia..
[edit]
resolved now..
Probably your mods. I have done same update resulting NO bootloop
Tracker31 said:
Probably your mods. I have done same update resulting NO bootloop
Click to expand...
Click to collapse
thx for the reply.. i dont have any magisk mod installed, apart from magisk itself..
(well theres the built-in systemless host module that i enabled, but i dont think this would cause any trouble as it has been there in the last few updates..)
and the same setup worked fine in the previous 10.5.4, 10.5.5 and 10.5.6 updates..
not sure what went wrong this time..
Try to download update package again. Maybe something broken
Tracker31 said:
Try to download update package again. Maybe something broken
Click to expand...
Click to collapse
already tried twice last night.. i had that doubt as well.. seems quite a few indian users are getting the update fast this time, so i thought maybe the wrong indian version was pushed to my device (global version)?
will try again tonight to see if anything changes.. thx..
Anyway it's not update failure, cuz it works for me
Tracker31 said:
Anyway it's not update failure, cuz it works for me
Click to expand...
Click to collapse
and your regional version is?
AC01BA
Doesn't matter which version you flash. I crossed flashed 3 times from EU to Global and vice versa. No issues.
Maybe you forgot to auto flash Magisk again after installing OTA. It is also recommended to flash Magisk to inactive slot after installing right away "before" reboot.
lekiaM said:
Doesn't matter which version you flash. I crossed flashed 3 times from EU to Global and vice versa. No issues.
Maybe you forgot to auto flash Magisk again after installing OTA. It is also recommended to flash Magisk to inactive slot after installing right away "before" reboot.
Click to expand...
Click to collapse
actually i did remeber to flash magisk to inactive slot after OTA before rebooting.. but seemingly im the only one with this bootloop, so probably certain config in my device caused the issue..
im now in the process of trying the OTA once more, and if this fails again, i shall try to just OTA without patching with maigsk..
if the device then boots, i shall root with magisk from scratch again then..
Strange, and yes must be something system-side. That's why they always say remove modules before flashing OTA or at least disable them. But in my case (only have another font module, iOS smileys and Ktweak) they didn't interfere with the last 2 Ota's. So updating went fine, but i might disable or uninstall them in future OTA's. To avoid such problems you are facing.
You need to uninstall all magisk mods before the update, buy you don't have any installed.
I also believe you need to download the full rom and not incremental. After the update you need to install magisk normally AND also to inactive slot before the reboot.
I haven't installed the latest yet but there previous updates are are installed without issues.
turned out to be a system modification i did back in the 10.5.4 times.. had no problem with it when updating to 10.5.5 & 6, so i totally forgot about its existence.. disabled the mod, updated to 10.5.7, and then enabled the mod again.. now everything is working fine..
Would you mind sharing what it was? I'm about to update and I got some system mods going on that could interfere, and I'm sire I'm forgetting about some too
ASTDEv3 said:
Would you mind sharing what it was? I'm about to update and I got some system mods going on that could interfere, and I'm sire I'm forgetting about some too
Click to expand...
Click to collapse
the magisk module created by smali patcher..
Riru core magisk module is causing random soft reboots in my Samsung Galaxy Note 10 Lite (running Android 10). Can anyone help regarding this issue?
I have tried both EDxposed and LSposed. Whenever I only tick the Riru core within magisk app then soft reboots occur randomly.
The developer of Riru said that it might be a Samsung's Kernel problem.
Does this issue occur in all the Samsung phones? Or a few phones face this issue?
Can this problem be solved if I upgrade to Amdroid 11?
I use riru core with no problems with android 11, so I guess that updating to android 11 will solve that problem
Newtonsart said:
I use riru core with no problems with android 11, so I guess that updating to android 11 will solve that problem
Click to expand...
Click to collapse
Is you device also Samsung Galaxy Note 10 Lite?
kaisar1994 said:
Is you device also Samsung Galaxy Note 10 Lite?
Click to expand...
Click to collapse
Yep
kaisar1994 said:
Riru core magisk module is causing random soft reboots in my Samsung Galaxy Note 10 Lite (running Android 10). Can anyone help regarding this issue?
I have tried both EDxposed and LSposed. Whenever I only tick the Riru core within magisk app then soft reboots occur randomly.
The developer of Riru said that it might be a Samsung's Kernel problem.
Does this issue occur in all the Samsung phones? Or a few phones face this issue?
Can this problem be solved if I upgrade to Amdroid 11?
Click to expand...
Click to collapse
Hello Kaisar, I'm too having the same problem with my Note 10 lite. Have you found the solution?
bajra said:
Hello Kaisar, I'm too having the same problem with my Note 10 lite. Have you found the solution?
Click to expand...
Click to collapse
I have not been able to find the solution.
Same here, I think that the problem is LSposed.
And I'm running latest update
Newtonsart said:
Same here, I think that the problem is LSposed.
And I'm running latest update
Click to expand...
Click to collapse
No, the problem is the "Riru" magisk module. Whenever I turn this module on, random reboots occur. Even if the LSposed is turned off in Magisk, then also I face the problem.
Newtonsart said:
Yep
Click to expand...
Click to collapse
How did you flash the boot.img after patching it with the Magisk original apk? For me it didn't get flashed. I had to patch it using canary version of Magisk before flashing the boot.img file.
And how long could you use Riru Core without facing the reboot problem? At first you said that the reboot problem wasn't there for you.
I am getting crazy to solve this problem. As I will not be able to use GravityBox without Riru.
kaisar1994 said:
How did you flash the boot.img after patching it with the Magisk original apk? For me it didn't get flashed. I had to patch it using canary version of Magisk before flashing the boot.img file.
And how long could you use Riru Core without facing the reboot problem? At first you said that the reboot problem wasn't there for you.
I am getting crazy to solve this problem. As I will not be able to use GravityBox without Riru.
Click to expand...
Click to collapse
I used Odin, And I had no problem flashing it.
I started having this problem one month ago, at first I had no problem with it.
It happens to me twice or 3 times a day. And it's pretty annoying.
I use Riru for LSposed disabling flag secure and Xprivacy Lua. I'm experiencing this issues with the module of LSposed disabled, so yeah, it must be Riru core
Newtonsart said:
I used Odin, And I had no problem flashing it.
I started having this problem one month ago, at first I had no problem with it.
It happens to me twice or 3 times a day. And it's pretty annoying.
I use Riru for LSposed disabling flag secure and Xprivacy Lua. I'm experiencing this issues with the module of LSposed disabled, so yeah, it must be Riru core
Click to expand...
Click to collapse
Did you update firmware before facing this issue?
kaisar1994 said:
Did you update firmware before facing this issue?
Click to expand...
Click to collapse
It started without updating. And now, using latest firmware it keeps happening
Newtonsart said:
It started without updating. And now, using latest firmware it keeps happening
Click to expand...
Click to collapse
The day before yesterday I flashed United Kingdom (BTU) version of firmware and rooted it by magisk canary version. Till now no reboot issue. May the Almighty make this work. You can try this.
It happened again. No hope for now.
Has anybody found the solution?
bajra said:
Has anybody found the solution?
Click to expand...
Click to collapse
Nope bro
Newtonsart said:
It started without updating. And now, using latest firmware it keeps happening
Click to expand...
Click to collapse
Zygisk LSposed is working I guess.
kaisar1994 said:
Zygisk LSposed is working I guess.
Click to expand...
Click to collapse
Yep, I'm using it. No random reboots
Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance
Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.
vinotux said:
Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance
Click to expand...
Click to collapse
Did you flash the DLKM module?
MarekPietrzak said:
Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.
Click to expand...
Click to collapse
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.
twistedumbrella said:
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.
Click to expand...
Click to collapse
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message. When I restored stock kernel, this issue no longer persisted. I will for sure try again custom kernel, but in two weeks or longer, as ROG phone 5 is my primary device and I need to stay in contact. I will try to reproduce this issue and grab logs. Now I can share my observation, that those crashes occurred when device was idle, and usually on charger.
JazonX said:
Did you flash the DLKM module?
Click to expand...
Click to collapse
Thanks for your response, do I need to? I flashed using FKM and not TWRP
vinotux said:
Thanks for your response, do I need to? I flashed using FKM and not TWRP
Click to expand...
Click to collapse
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
MarekPietrzak said:
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message.
Click to expand...
Click to collapse
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.
twistedumbrella said:
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.
Click to expand...
Click to collapse
Great, I'll just reevaluate when the new update rolls out, thank you .
vinotux said:
Great, I'll just reevaluate when the new update rolls out, thank you .
Click to expand...
Click to collapse
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.
twistedumbrella said:
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.
Click to expand...
Click to collapse
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .
vinotux said:
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .
Click to expand...
Click to collapse
Fair enough. It shouldn't be on you to do it anyway. With any luck, i'll have debugging sorted out before the end of the weekend with proper instructions to avoid all the guesswork.
Asus Proprietary Logs
In trying to debug kernels, I realized that Asus has rerouted the location of some of the more important logs to make them "easily" accessible. Disclaimer: This is not a complete list of every file included, but lists the more "useful"...
forum.xda-developers.com
An error happens, the kernel logs the issue, the device reboots. This is how things are supposed to work. When disabling debugging, an error happens and the device reboots. The logging step is skipped, but life continues.
The problem is when debugging is partially disabled, but still attempting to write. This is basically why there is a "waiting for ramdump" message. It is waiting for the logging to complete to proceed to the next step.
Asus Power Debug: guard debugging so it can be disabled · freak07/[email protected]
Contribute to freak07/Kirisakura_ANAKIN_ROG5 development by creating an account on GitHub.
github.com
This commit set the stage for a future break, which happened in the .176 update when printk_buffer_rebase replaced get_last_shutdown_log.
Hi, just a quick update.
I had been experiencing major issues and the waiting to flash full ramdump debacle had gotten extremely frightening. The phone wouldn't recognize the IMEI of the device, wifi wouldn't work, etc. The error happened multiple times a day. I took it to ASUS and they basically told me to f off due to my phone being unlocked.
As a last resort, I flashed the .151 RAW firmware and I swear all of the problems vanished. If I was a betting man, I'd say that the .176 update caused all of the problems since I've used the device for a week now without any problems thus far.
Major thanks to @twistedumbrella and others for replying to this thread.
I don't doubt you are right about that. 188 improves things a bit, but they definitely broke something significant in 176. I have never crashed as much as on that build.