Related
Hello there! i'm making my forum debut while extremely confused as to how to proceed with fixing my Verizon Galaxy S3, running the stock android JB 4.3. So there is no custom ROM.
I realize that this may or may not be similar to a plethora of posts about apps crashing around the time android 4.3 was released but i've upgraded to 4.3 less than a month ago. After diving through countless forums, i couldn't find one that addressed the same problems that my device had. They were all similar, but the solutions posed in those threads did not work with my device. Plus the problems i have are not isolated to one app.
I had just recently upgraded to android 4.3 which had unrooted my previously rooted device. After using Chainfire's method of rooting the SCH-I535, utilizing saferoot, i then installed the Xsposed Framework and that was really where my troubles began. A few days had passed while i was tinkering with a few modules like XBlast tools, XHaloFloatingWindow, Xposed Torch, and Wanam Xposed, and i had a good sense of what mods interfered with other mods and it was only last night when the problem first arose.
Without warning, a game that i play all the time stopped working. Literally in the time span of 6 hours (i was sleeping) something happened and the beginning of my problems started. Every time i would open the app, the app itself would close and i would get a message saying, "Unfortunately, Valkyrie Crusade has stopped." It was only a few hours later did i realize that Pandora, an app i use every day, suddenly stopped working and provided me with the same message. There was no error ID, and clearing the cache/data, reinstalling the apps, did not work. Once it became 4-5 apps that i normally use to get the message, i tried uninstalling the mods as well as the xposed framework but that also did not work. I also tried restoring the game as well as the other apps to a backup i'd made just the week prior with Titanium Backup but i still had the message coming up and the apps still did not work.
As a last resort i did a factory wipe/reset. During the initial set up, i opted to allow google to restore my apps (which i'm not sure i should have done) and after everything was restored, i tried using the apps, and i was met with the familiar message "Unfortunately, (app) has stopped.". I have run out of ideas. While i'm more tech savvy than most, i'm really just a novice when it comes to Android. How should i approach my next step? If anyone needs logs or anything like that, if you would be so kind as to walk me through the steps to get them.
Thank you, thank you, thank you in advance.
EDIT - 2/10/14
I have successfully resolved the issue (or at least, removed it) from happening. I bricked my phone but thankfully i was able to get into download mode.
Follow this guide! http://forum.xda-developers.com/showthread.php?t=2586319 - just be aware, this will delete all of your apps. backup all your propers and jump in.
This is the only method that i had success with. Other methods i tried are explained above and in the comments. Good luck and i hope everything works out!
If you had the Xposed frameware installed and you also installed Wanam xposed, this will help if you are experiencing apps crashing. I'm no expert, but i'm really glad to have resolved this as quickly as possible. I couldn't have done it without everyone! You guys literally kept my sanity healthy during this whole ordeal.
*NOTE* - The link to the guide above will lead you to a stock rom of android 4.3 for the SCH-I535. I'm not sure about other samsung devices but one user had success with a SCH-I605 (galaxy note 2) in the comments.
*ANOTHER NOTE*- i'm not in any way explicitly saying that the xposed framework and wanam xposed module are the cause of this glitch. Frankly i have no idea. But they seem to have been problems for a few people, myself included. If you want to explore this further, i'd suggest going to each of the respective forums. For me, i'm going to make sure i have a proper Nandroid before i do anything crazy. Lesson learned.
Again, Thank you!
PS- since i'm newer to this forum, i have no idea how to edit the title of this Q....haha if someone could let me know....that would be great.
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
daoist said:
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
Click to expand...
Click to collapse
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
awstuder said:
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
Click to expand...
Click to collapse
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
ATGkompressor said:
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think i'll try that next. I used to have TWRP but had to flash the stock recovery just to upgrade to 4.3. I'll try to get a clean copy of stock OS, flash and just start over from scratch. I'll be sure to let you guys know if i got it to work.
ran into a bump in the road. flashing a stock copy of android 4.0.4 did not work. Browsing through a few forums informed me that i'm unable to downgrade after i've taken the 4.3 upgrade. so next i tried to flash TWRP to boot into recovery mode and flash a rom from there. That didn't work either. I kept getting an authentification error.
As of now i can't get into download mode anymore. I get the yellow triangle saying Verizon detects unauthorized software. I'm able to get into recovery mode but i'm not sure what i can do with stock android recovery....
what can i do from here?
EDIT: I am able to get into download mode. I'm not sure why i wasn't before and now i am...
EDIT2: I have tried flashing the "official" stock android 4.3 but it fails everytime. I have also tried flashing twrp and cwm but i get a red Secure Check Fail: recovery. I suspect the bootloader has been locked. I'll look into ways of getting it unlocked again...
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
awstuder said:
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
Click to expand...
Click to collapse
Same here. Disabling all xposed modules didn't work. Disabling xposed entirely didn't work. Doing both and then uninstalling didn't work. My guess is that along the way either xposed or wanam xposed made some sort of change that it can't roll-back when it's disabled/uninstalled.
I resorted to taking a TiBu update of everything and reflashing.
Once I get my battlestation fully armed and operational I plan on taking frequent nandroids and seeing if I can replicate the issue. Once I do that, (if I do) I can compare the last known good nandroid to see what messed up.
BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't able to do this right away since had class in the morning but as soon as i got home, i did this and it fixed my soft-bricked phone.
thank you thank you!
Now back to the problem at hand......let's see if the problem still persists.
It's completely fixed! No apps (so far :fingers-crossed have crashed and i'm able to happily play my games again! sigh. that was refreshing.
Thank you to everyone! i will edit my first post to outline what i did and how i fixed it, finally....
during saferoot process your suppose to update SU then continue with finishing up the root process..took me several hours to figure this out..no errors now since I figured this out
Sent from my SCH-I535 using XDA Premium 4 mobile app
That... Actually makes sense. When I used safe root I didn't check for any other updates because I assumed the program took care of that for me. That and because when I opened su there were no notifications to update. So maybe that could be a solution as well.
Sent from my SCH-I535 using xda app-developers app
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
These are the steps that I took to finally get systemless root and xposed. Android pay works now. I thought I would share this. It took me over 5 days of many many wipes and restores. I will also discuss some of my phone quirks in here. The reason why I am discussing these quirks is to explain that every phone is very very unique and if people do not have enough experience, they will end up with very different results
Standard disclaimer: Not responsible for anything that goes wrong with your phone
I also would consider this to be moderate difficulty, its not really for beginners due to multiple pre reqs and terminology
I would consider this very early beta at best, sometimes xposed does not stick, so far I think I finally figured out how to make it stick with every reboot.
I- My phone:
I have V10_H901_V20J_Stock_Custom_2e-signed , so obviously I had to go through the pain of understanding that thread. If your phone is already on that rom , then you must have TWRP in place by now. That of course is a prerequisite.
II- Visit the following threads, Credit goes to all the developers there, I am merely putting it as a write up.
A- This is the main thread, honestly, didn't love the instructions there, hence why I am doing this.
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
you will need to download the following from that thread ( but I put in the links to the right files)
There is no need to place in any specific folder, I usually put every thing on my external SD
1- Magisk: http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get
Place it anywhere you can easily access it.
Edit added 09/11/11: magisk controller app : http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
2- PHH systemless SU: http://forum.xda-developers.com/attachment.php?attachmentid=3847928&stc=1&d=1471642336
PHH super user app to work with systemless root :
https://play.google.com/store/apps/details?id=me.phh.superuser
B: Xposed systemless thread: here is the main thread
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
1- Download Systemless xposed: xposed-v86.5-sdk23-topjohnwu.zip form : http://forum.xda-developers.com/attachment.php?attachmentid=3847909&d=1471640756
2- download the xposed material design app to control xposed:
http://forum.xda-developers.com/devdb/project/dl/?id=19668&task=get
Steps - This is what worked best for me, I have heard numerous times on the v10 stock rom thread that our roms come in with systemless root. I can never get that to work systemless. If you know a better way, feel free to share the knowledge.
1- Back up ! use TWRP, Here is quirk number one from my very special phone: TWRP restores fail if the phone is hot. They do not restore properly. Do what you need to do to keep your phone cool if you need to restore. I have tested this about 5-8 times in the past 3 days. If my phone is pre-cooled ( use your imagination ), it restores 100 % without missing apps or errors. If it gets hot, then I get app crashes, errors, and all sorts of corruption.
2- Uninstall xposed if you have it running on your device - THIS IS A MUST make sure you use the official uninstaller that came with your xposed version
3- unroot your phone. use SuperSU app to unroot your phone: Do restore the system boot when prompted, do NOT restore original recovery, you need twrp obviously.
4- Boot into recovery manually: Now I feel like this is most confusing part about LG phones, and its never really well written:
Power down the phone
hold the volume down
with the volume down being held ( do not let go) , press the power button, until the LG logo appears, as soon as that happens, let go for 1/2 second then press the power button again ( this whole time the volume down button should be pressed ). You will get two prompts of warning, if you are successful, about the device being erased, it will not get erased You will simply just boot into TWRP
5- Flash the following in order , do not queue, TWRP is finicky at best for our phones , never queue
- Magisk from step A - 1
-phh super user A - 2
6- reboot phone. Your phone is now systemless rooted, the root can be turned on/off on demand.
You will find magisk app on your phone, do not start , it will simply crash
you will need to install the PHH super user app from step A- 2 , this is a simple apk from the play store.
then you can mess with magisk if you would like, I will explain it's options later
7- Uninstall whatever xposed controlled app you used to have, install the material design xposed app controller from B-2
8- now that you have root, reboot to recovery, using whatever app you use to simple reboot into recovery (quirk alert: I can never find a way to include reboot to recovery from the power menu, no matter what mods I have)
9- flash systemless xposed from B -1 . wipe dalvik/cache 3 x , wait for your phone for 500 years to boot up
10- you are now systemless. go into the xposed app and check all the modules to re-enable them
11- VERY VERY IMPORTANT: xposed does NOT stick with simple reboots, soft reboot, or recovery reboot.
09/25/16 : update. Xposed now trips safety net. Even if it's systemless. Some reports also say Magisk will trip it. Sorry but this guide is now obsolete.
Great guide works perfect!!!
I'm running this systemless train [powered by magisk] really smooth. I'm running rooted stock MM with no issues at all. I can reboot with G4tweakbox mod, Xposed sticks every time and is very stable.
This probably has been asked and answered a thousand times, but since we can unlock the bootloader can't we just flash TWRP after that and than do these Step?
No
johnwayne007 said:
This probably has been asked and answered a thousand times, but since we can unlock the bootloader can't we just flash TWRP after that and than do these Step?
Click to expand...
Click to collapse
Not really
Here are the problems we faced with MM onwards
1- LG disabled the flash commands with MM, even though its is an unlocked bootloader. Hence why you have other threads with instructions on how to circumvent the good old fastboot flash commands.
2- TWRP needs compatibility with the v20J update. I am not sure if we have any devs working on that
So we are in an appleisk like situation with the newest update. No dev = no further progress, unless you want to loose root and recovery . You have the wonderful people here at XDA to thank for that, who constantly b**** at developers for that.
I Have tons of bugs on marshmallow , but I refuse to update until this situation is fixed. Next phone is nexus. I am so tired of all this BS with all the other manufacturers.
jmichaels1982 said:
11- VERY VERY IMPORTANT: xposed does NOT stick with simple reboots, soft reboot, or recovery reboot.
You need to power down your phone fully. Then power up . That is my personal experience. and I have tried it over 5 times and now it sticks with every boot.
Click to expand...
Click to collapse
just wondering if you could elaborate on Xposed not "sticking"?
dimm0k said:
just wondering if you could elaborate on Xposed not "sticking"?
Click to expand...
Click to collapse
It will say in the xposed app that xposed is installed but not active.
Sent from my LG-H901 using Tapatalk
jmichaels1982 said:
It will say in the xposed app that xposed is installed but not active.
Click to expand...
Click to collapse
Are you using the layers app with hydra installed? Removing it might help you out. Once I did that I had no issues keeping Xposed to stick and may be a bug with v3
This was very well written and easy to follow. Systemless root and xposed are running perfectly! Thank you
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
apologies
Sippi4x4man said:
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
Click to expand...
Click to collapse
Sorry man , I fixed all the links.
I feel like an idiot....I've been trying this for 2 days and no success. Used KDZ to get to bone stock J build, then used the .tot updrade to get TWRP and rebooted, now I have an unrooted stock rom with twrp. I adb reboot into recovery and successfully flash magisk and then successfully flash phh superuser but after I reboot I don't have root.....Can anyone assist?
EDIT: Nevermind.....apparently I was flashing Magisk v3 and not v6...not sure how that happened. I rebooted into TWRP, flashed magisk v6 and then phh superuser and I now have root.
Thank you for the guide.
Sippi4x4man said:
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
Click to expand...
Click to collapse
Trying opening the link outside of xda labs app. I loaded the link in Firefox and now it downloads properly
Can some one provide me an explanation of what it means to have a systemless setup and the benefits of that!?
I installed as you instructed and It mostly works great. Thank you. May I ask what settings you use for Viper4Android (External Speakers)? I am not sure on how to get it working. I installed the systemless version you posted. I am also using the same ROM you are. However when I enable Viper4Android, I notice no difference whatsoever in the sound of my external speakers... Just playing an mp3 via Google play music. Any info would be greatly appreciated. Thank you.
Blur
For the life of me I can not get this working with the systemless xposed installed. With just root everything is fine. As soon as I install xposed it immediately fails. I tried the newest version and the version linked in the directions. Viper also works fine. Just not xposed.
nookie1916 said:
For the life of me I can not get this working with the systemless xposed installed. With just root everything is fine. As soon as I install xposed it immediately fails. I tried the newest version and the version linked in the directions. Viper also works fine. Just not xposed.
Click to expand...
Click to collapse
OK so this is redundant,so I apologize in advance. But
1- you can not install xposed over the same version without creating problems. You can only go up in versions when installing. Not sure why but this is my personal experience.
2- when all else fails, uninstalling magisk and xposed and re install. If still fails then delete your system partition and restore an older back up (hopefully you did back up). From there repeat the process. Always start with fresh files if it pertains to your problem. Meaning, Re-download xposed systemless.
Good luck
Sent from my LG-H901 using Tapatalk
jmichaels1982 said:
OK so this is redundant,so I apologize in advance. But
1- you can not install xposed over the same version without creating problems. You can only go up in versions when installing. Not sure why but this is my personal experience.
2- when all else fails, uninstalling magisk and xposed and re install. If still fails then delete your system partition and restore an older back up (hopefully you did back up). From there repeat the process. Always start with fresh files if it pertains to your problem. Meaning, Re-download xposed systemless.
Good luck
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Actually found out Google updated safenet the other night where it stopped working with xposed installed with magisk. Without xposed everything still passes. Had to use the other method of not using magisk and using suhide and that method still works with everything.
jmichaels1982 said:
I Have tons of bugs on marshmallow , but I refuse to update until this situation is fixed. Next phone is nexus. I am so tired of all this BS with all the other manufacturers.
Click to expand...
Click to collapse
It'll have to be a Nexus 6p, or older because the Pixel phones will supposedly have locked bootloader.
Thanks for the great step-by-step directions!!! Had been reading all of these related threads trying to make sure I knew what order to do everything. Followed the steps as written. Checked when I got root, before installing xposed, and SafetyNet showed green. Installed xposed and rebooted - only issue I had here was when it finished updating apps and got back to my home screen - all of my app shortcuts on all screens were gone, including the bottom line. The widgets I had previously were still there. So it just took a few minutes to re-do all my screens - not that big a deal to get all this done!
But then I had the same problem as nookie1916, SafetyNet and Android Pay would not work now. So I tried turning off the xposed framework and rebooting, and that worked - SafetyNet showed green again and I was able to load my Chase Visa onto Android Pay. Then turned xposed back on and rebooted.
So it's not quite the way I wanted it - but I use xposed features much more than I need Android Pay.
Thanks for your help!!!!!
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk