Related
Hey guys whats up was messing round with my phone today, and well I got some kinda bug for the life of me I do not understand. I know this kinda bug gets to lots of people. Maybe possible to a malicious app? Or corrupted system files? No idea.
Information:
model : HTC Inspire 4g
Kernel : 3.0.83 Jellytime_42_R9-gee5143f
Android v : 4.2.2
ROM : JellyTime_R11
Baseband : 12.69a.60.29U_26.17.14.11_M
Moments just before the bug appeared:
Was just browsing google play installed talkatone, clueful, Uninstalled some apps, wifi related stuff, and others. (getting hard to remember)
Booted into recovery cleared dalvik cache, and cache. Rebooted. System updated as usual
Installed exposed module root cloak, and master key vulnerability fixes, Rebooted. Shortly after started noticing bug. Upgrading on reboot, it doesnt go through every app. just a few. Perhaps something got corrupted? Hoping someone with more experience in debugging can help me out. I fails to do a recent backup just b4 doing all of this. I have a backup but it's getting old, and kinda wanted to try to fix whats happening if possible. Any insight on this would be greatly appreciated
Now I'm not 100% sure this is exactly everything I did, I'm pretty positive it was along those lines, and round bout that order.
Attaching a partial catlog, can anyone help me understand whats happening in this log? I can get more complete log if needed.
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
You can try a factory reset.
ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?
I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.
Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.
Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.
fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.
Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.
A bit of history, I was running KK Cloudy 1.2 for a while with xposed and I'd get a 1 or 2 auto reboots from apps/system crashing. I figured this was probably because KK was old and runnign xposed modules.
Recently I clean flash upgraded to 'D850 20f Stock ROM Debloated' Lollipop ROM by cmulk.
I'm still getting one or two auto reboots a day from system crashing. Is this normal?
Even on other ROMs as a more general question how often does your guys system auto reboot from a crash? How often do you reboot manually?
Just so everyone knows how clean of flash I did...
I went through the process of restoring the factory image using LG Flash Tool and TOT file. Then I immediately stump rooted, flashified TWRP, updated TWRP to latest twrp-2.8.5.1_d850-bumped.zip, wipe in TWRP, installed D850_20F_2.0.1.c1.13-00050_Modem.zip and then Debloated_Stock_20f.zip. Then let PS reinstall apps and configured everything manually. Didn't even do a TB restore.
So is this normal behavior for android? Or just the LG G3? Or just me? Thanks!!!
Too early for me to tell. Installed yesterday morning, clean install. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
JeffDC said:
Too early for me to tell. Installed yesterday morning, clean instal. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
Click to expand...
Click to collapse
Thanks for the reply. Let me know how it goes. I heard about the led issue some folks are trying to get some logs to debug it.
I went through the process again and this time I installed a lot less apps. I'm going to see if that helps.
I didn't have any random reboots until I installed Trickster.. which was stupid of me since there's no BusyBox on the 20f release by AutoPrime
As soon as I uninstalled it after 1 reboot it hasn't happened again.
So if you've got Trickster or any other Kernel Tweak apps installed.. try uninstalling
Two days, no reboots.
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped system, cache, and data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
EDIT: Forgot to mention that I wiped system and cache also.
cameronkelley28 said:
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
Click to expand...
Click to collapse
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
JeffDC said:
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
Click to expand...
Click to collapse
Forgot to include that I wiped system and cache also. So glad I waited as well. It is mind blowing how stable it is, especially with an alpha version of Xposed and so many alpha/beta modules. Just installed the beta versions of Greenify and AppSettings also, so we'll see if that introduces any instability.
After restoring apps with their data, were there any apps that you had to clear data for due to issues? Or have they all been solid?
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
slojam said:
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks slojam I will give this a try tonight.
running cloudy 2.2 without any crashes. Thanks cloudyfa
illusivenick said:
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
Thanks slojam I will give this a try tonight.
Click to expand...
Click to collapse
This is from skeevydude @ http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610/page13
I'm sure someone will come along who can provide more detail. It does not take long for a log to fill. I did my first few today and an 800K file was about 28 pages long. That is a lot to look through unless you know what to search for.
********************
skeevydude
Anyways, as far as the logs go, the easiest way is by using adb logcat on a PC. Look for guides on how to set all that up....then again, your rooted on LP so that should be done already
The first command to run is "adb logcat *:W >> C:\bootwarn.txt". Enable ADB, power off your phone, plug your phone in to your computer, and let it boot up to the home screen and let it sit there for a minute or two. End the command by using "control+c".
Next, run the command "adb logcat *:W >> C:\notificationwarn.txt" while intentionally doing things that should make your notification light blink -- email yourself, have someone text you a few times, call you, etc. End the command the same way. We need to catch the warnings and errors that are being thrown, so hopefully doing that will help find it.
To help you out on the commands "*:W" tells logcat to only display warnings and up and ">>" tells it to append to a file located where you tell it to be....">" all alone will overwrite a file if it's there.
Anyways, on both those commands, do them twice only changing out the ":W" for ":E" so it'll filter out errors and up.
******************
What worked for me in the first part of his instructions, was to have the command ready/typed into the command prompt on the PC but don't hit the return yet. Then, with the phone off, plug into the computer, wait for the computer to register the phone/acknowledge it, just turn on the phone, and once it starts up press the return key on the PC keyboard to launch the commend. The log will catch things as the phone starts to boot. I tried with the specific directions, but for some reason the PC could not find the device, other than how I detailed here. Just for that first command where the phone is off.
Good luck
Hey guys,
I'm in weird situation. I was debating with myself for a long time whether to unlock the BL or not (Verizon) and decided not to - because I want things to just work.
So I left the system as is and funny as it sound - Android Pay is not working, although I didn't change anything with the phone. It's completely stock, no BL unlock, no flashing no nothing. The only thing I did do was to flash an OTA.
Any thought? Any idea how to fix?
SafetyNet Helper shows "CTS profile match: false".
Another weird issues I'm having that might be related:
ֿIf I clear Data for Android Pay I get "MTP Host has stopped" message (force close message). Then - I can't charge the phone and I need to restart it.
After restarting though - The system goes back to the previous version (October patch)! That's the one that was before the OTA. Then I get the android upgrade notification (for November, the version I was on when it all started).
SUPER WEIRD!
don_alberto said:
Hey guys,
I'm in weird situation. I was debating with myself for a long time whether to unlock the BL or not (Verizon) and decided not to - because I want things to just work.
So I left the system as is and funny as it sound - Android Pay is not working, although I didn't change anything with the phone. It's completely stock, no BL unlock, no flashing no nothing. The only thing I did do was to flash an OTA.
Any thought? Any idea how to fix?
SafetyNet Helper shows "CTS profile match: false".
Another weird issues I'm having that might be related:
ֿIf I clear Data for Android Pay I get "MTP Host has stopped" message (force close message). Then - I can't charge the phone and I need to restart it.
After restarting though - The system goes back to the previous version (October patch)! That's the one that was before the OTA. Then I get the android upgrade notification (for November, the version I was on when it all started).
SUPER WEIRD!
Click to expand...
Click to collapse
What if you uninstall the AP app and reinstall?
quangtran1 said:
What if you uninstall the AP app and reinstall?
Click to expand...
Click to collapse
Tried that. Also deleting data. It's unrelated because the SafetyNet doesn't work.
Anyway, I flashed a factory image and It works now.
I have rarely had any bootloop on my previous devices, so I'm not sure if this even counts as bootloop:
An hour ago I found my Pixel 2 (stock 8.1, Magisk 14.5 unmodified, TWRP 3.1.1) restarted itself (with the internal error message it's hard to miss). So I hit OK and enter the pattern to unlock. Upon unlock it reboots and arrives at lock screen again. Another unlock would trigger another reboot, over and over.
Luckily, I had Magisk uninstaller stored on SD card so I went in recovery to flash that, which seems to have restored the backed up boot image, and the phone is properly functional again. Then I flashed Magisk and it's all fine now.
I'm not attributing this issue to Magisk but just wonder if anyone else has seen this issue before. With lock screen being properly loaded, I'm not sure if this even counts as a bootloop.
Another factor to consider is, about two hours before all this happened, I installed AdAway to modify the host file. Don't know if that could be the reason, but now I've modified the host file again, will see if this issue comes back.
I just started having the same problem about the same time. I did a complete shutdown from the lock screen and when it fully booted, it was fine overnight, but it started acting up again this morning, so I did a complete shutdown again. It hung on the shutdown screen, so I had to do the hard reboot. Doing fine again, for now. I also have Magisk and AdAway, but I'd had both of those active for a few days before this started up.
I has something similar but different happen. After updating to 8.1 with magisk, I updated my hosts with adaway. I then had it hang on shutdown (this was the first time this had happened). Hard reset and rebooted and everything seemed to be fine. I then put it on the charger overnight, only to wake up the next morning and find it in the recovery menu saying there was an error booting the system and recommending a factory reset. I ignored that and rebooted, and haven't had any other issues since, but that one was weird.
It's something to do with magisk 14.5 456 beta. I've had the same boot loops, reverted to stock boot.img and problems went away
I haven't has this issue since I posted. To be clear, the problem I had could not be solved by a hard reset - it actually reboots itself every time I try to get past the lock screen for the first time after the previous (self) reboot. It's exactly a bootloop except that the phone makes it into the OS instead of failing to boot.
It can be Magisk or Adaway, no worries. I just pray it's not a hardware issue.
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
I'm still using Magisk 14.3 on 8.1, "Flash" kernel, no issues.
I've not had this issue since I posted about it. I uninstalled one live wallpaper app, which I'm not sure did the trick or not.
froader said:
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
Click to expand...
Click to collapse
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
cswithxda said:
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
Click to expand...
Click to collapse
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
froader said:
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
Click to expand...
Click to collapse
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
cswithxda said:
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
Click to expand...
Click to collapse
Thanks for confirming. I wasn't sure if that was present flashing via TWRP, but makes sense that it would.
Same exact "Internal error" warning and occasional boot loop after upgrading the Pixel 2 (not XL) to 8.1 from Magisk 14.5.1456 using TWRP 3.2.1.0. Also an AdAway user. Glad to hear I didn't mess it up and it's just a quirk of the method and the alpha/beta stages. Hopefully this resolves soon as I hate guessing whether my device will go belly up at random. Seems like Flash kernel with Magisk 14.3 may be ideal - any other confirmations that this is a stable method?
I'm having this same issue as well! Using Magisk 14.5 1456, with the latest TWRP non-beta, and the Unified Hosts Adblock module. Randomly my phone goes into a soft reboot loop like your describing. If I hard reboot using power + volume up it seems to fix it for a time, then it happens again at a, seemingly, random time. It's crazily frustrating. The only other things I have that involve root are a terminal app, Drives roid, and CoSy to sync Facebook contacts. I also had Substratum using the root method, but I uninstalled that today wondering if that was the cause.
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
cswithxda said:
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
Click to expand...
Click to collapse
Were you able to recover from the bootloop at all without uninstalling? For me I was able to force restart it, it would be fine for a few hours then it would bootloop again.
Additionally, I uninstalled Magisk and flashed the stock boot image as well and so far it hasn't come back. I still have TWRP.
Not at all, hard reset still sees the same reboots over and over, so I had to try something. And the only thing I found was the Magisk uninstaller on the SD card lol. I then uninstalled the Magisk and reinstalled it, and the issue has not come back so far.
I'm having that boot loop. I'll try uninstalling magisk
Sent from my [device_name] using XDA-Developers Legacy app
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Interesting about removing AdAway. I had a hosts adblocker as well, I wonder if that has something to do with it.