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.
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 have a rooted 12.2. I was reading another thread that random reboots occur when installing SuperSU and not having it disable Knox. I did the reinstall of SuperSU, but I wasn't prompted if I wanted to have it disable Knox or not (unlike the first time I installed it). Anyway, I really dislike the random reboots because it kills the battery. Can someone advise how I can get SuperSU to ask me about disabling Knox?
Or... show me where to download the stock firmware for a USA Galaxy Note Pro 12.2? Or would a factory reset through the Recovery (Home+Volume Up+Power) unroot and bring me back to regular stock? Thank you so much.
I had the same problem.
But it was gone when i installed the Xposed framework, and the Wanam Xposed add-on.
There is an option in the expirimental options to fix the random reboots.
There is also an other add-on for Xposed called the Samsung Kitkat SystemServer Crash Fix.
More info about that is here: http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
After I deleted all the Knox apps my random rebooting quit.
1seniorgeek said:
After I deleted all the Knox apps my random rebooting quit.
Click to expand...
Click to collapse
What Knox apps are there? I didn't download any. What did you use to remove them?
On the sidenote, I seemed to have borked my root by trying to uninstall SuperSU (it hanged) and I did a hard reset. Now I need to find the binary... Assistance greatly appreciated! Or would it be easier to do a factory reset and start from the beginning?
CyberDie21 said:
I had the same problem.
But it was gone when i installed the Xposed framework, and the Wanam Xposed add-on.
There is an option in the expirimental options to fix the random reboots.
There is also an other add-on for Xposed called the Samsung Kitkat SystemServer Crash Fix.
More info about that is here: http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
Click to expand...
Click to collapse
Do you mean this one? http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053/post24267797
CyberDie21 said:
I had the same problem.
But it was gone when i installed the Xposed framework, and the Wanam Xposed add-on.
There is an option in the expirimental options to fix the random reboots.
There is also an other add-on for Xposed called the Samsung Kitkat SystemServer Crash Fix.
More info about that is here: http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
Click to expand...
Click to collapse
I installed both of which you mentioned. By experimental options, do you mean: Disable resource hooks? If not, I don't see the option... Thank you for your help!
Okay, cool. I think I am able to avoid reboots now!
For those who have issues... I installed SSCF Xposed, Xposed Installer, and Wanam Kit. Now I just get notifications when crashes are avoided (which I can hide from now on).
Seems like it would be a lot easier to uninstall the Knox program(s), but I don't know what those are.
Thanks for everyone's help!
Makoto1 said:
Okay, cool. I think I am able to avoid reboots now!
For those who have issues... I installed SSCF Xposed, Xposed Installer, and Wanam Kit. Now I just get notifications when crashes are avoided (which I can hide from now on).
Seems like it would be a lot easier to uninstall the Knox program(s), but I don't know what those are.
Thanks for everyone's help!
Click to expand...
Click to collapse
Drat. It reboot on me this morning. I had it plugged in from charging overnight and I flipped my screen cover open to wake it up and it froze and rebooted.
Anyone have any tips? I would flash the stock USA rom and start from scratch if I could find the rom. Would a factory reset from recovery mode bring me back to stock pre-SU? Should I have SuperSU close root before doing a factory reset? Thanks.
Makoto1 said:
Okay, cool. I think I am able to avoid reboots now!
For those who have issues... I installed SSCF Xposed, Xposed Installer, and Wanam Kit. Now I just get notifications when crashes are avoided (which I can hide from now on).
Seems like it would be a lot easier to uninstall the Knox program(s), but I don't know what those are.
Thanks for everyone's help!
Click to expand...
Click to collapse
Hello, I solved by deleting the Knox files that are located in some folders of /system.
roys_ said:
Hello, I solved by deleting the Knox files that are located in some folders of /system.
Click to expand...
Click to collapse
Thanks, I'll try that if I still get the reboots. Last night I did a factory reset and was able to get the prompt for SuperSU to ask about disabling Knox (which I hit cancel). So far no reboots. I'll be slowly building my app collection to see if it may be related to an app.
Well, did it work? I am having the same issue and I am not sure if I should go back to stock and not disable Knox with SuperSU or I should remove Knox all together. This is driving me batty. Thanks in advance.
Knox is the problem
Makoto1 said:
I have a rooted 12.2. I was reading another thread that random reboots occur when installing SuperSU and not having it disable Knox. I did the reinstall of SuperSU, but I wasn't prompted if I wanted to have it disable Knox or not (unlike the first time I installed it). Anyway, I really dislike the random reboots because it kills the battery. Can someone advise how I can get SuperSU to ask me about disabling Knox?
Or... show me where to download the stock firmware for a USA Galaxy Note Pro 12.2? Or would a factory reset through the Recovery (Home+Volume Up+Power) unroot and bring me back to regular stock? Thank you so much.
Click to expand...
Click to collapse
I have a Galaxy Tab Pro 12.2 rooted with Chainfire stock rom. I started getting random reboots soon after root and yes I did select yes when super su asked to disable knox. Never had a problem with this on a Note 4, S5, or Note 8.
I tried most of what everyone has discussed except re-flash and factory reset. I also uninstalled super su, enabled knox, re-installed super su. But this time super su did not ask to disable knox.
Re-enabling knox did not stop it. I installed xposed server crash tool and got the following in xposed logs when it would prevent a crash:
0:com.sec.knox.seandroid/1000
I then used terminal emulator to disable:
Su [enter] (this brings up super su authorization window, select enable)
PM disable com.sec.knox.seandroid [enter]
You can also disable in settings > security > device administrators > uncheck knox
This did not work, I was still getting the same crash report. So I decided to completely remove knox, not just disable it since there are several modules that work with the knox app.
I used System App Safe Remover for rooted to remove. It backs the files up on your SD card versus just delete so you can later restore if necessary.
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store
Select these files and unistall them.
Reboot and you are done.
Now, no more random reboots. I hope this works for you.
My Fix
Makoto1 said:
I have a rooted 12.2. I was reading another thread that random reboots occur when installing SuperSU and not having it disable Knox. I did the reinstall of SuperSU, but I wasn't prompted if I wanted to have it disable Knox or not (unlike the first time I installed it). Anyway, I really dislike the random reboots because it kills the battery. Can someone advise how I can get SuperSU to ask me about disabling Knox?
Or... show me where to download the stock firmware for a USA Galaxy Note Pro 12.2? Or would a factory reset through the Recovery (Home+Volume Up+Power) unroot and bring me back to regular stock? Thank you so much.
Click to expand...
Click to collapse
I fix the problem by plugging in achager. Looks like it a battery problem. Minestarts rebooting and flikkering when my battery drops below 30%.
same here
tykenicol said:
I fix the problem by plugging in achager. Looks like it a battery problem. Minestarts rebooting and flikkering when my battery drops below 30%.
Click to expand...
Click to collapse
hey there, i Thought i was the only one. when my battery is bellow 30% the tablet begins to constantly reboot after the samsung logo logo. i found that it only happens when is on battery because i do heavy multitasking tests with the charger plugged and works perfectly, but a simple app when in battery makes the device crash. also found a perfect app to make the tablet crash and it is camera fv-5 (when in battery and bellow 30%), currently using ver 2.68. has anybody the same problem. did you fix it tykenicol?
meneses.leonardo said:
hey there, i Thought i was the only one. when my battery is bellow 30% the tablet begins to constantly reboot after the samsung logo logo. i found that it only happens when is on battery because i do heavy multitasking tests with the charger plugged and works perfectly, but a simple app when in battery makes the device crash. also found a perfect app to make the tablet crash and it is camera fv-5 (when in battery and bellow 30%), currently using ver 2.68. has anybody the same problem. did you fix it tykenicol?
Click to expand...
Click to collapse
You can try this: add some thing thick like paper on top of the battery connector and secure it with a tape. A direct pressure from the rear cover to the battery connector stops the problem, then you have a cracked solders of battery connector. A simple re solder this connector will fix your problem.
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
Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?
Rooted LG Lucky
I rooted using kingroot version 4.8.0 I could use the stock Rom have no download if anyone could help thanks. Its a straight talk lg lucky running 4.4.2 kitkat I'm no computer whiz and I couldn't figure out how or what I needed phone works fine . now I just want to be able to do a factory reset safely if need be only deleted stock apps that I don't use nothing important I hope.
boct1584 said:
Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?
Click to expand...
Click to collapse
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.
STOCK firmware??
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??
bonnis.phone said:
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??
Click to expand...
Click to collapse
Depends on if yourlucky was rooted and if you deleted files you should have
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.
Click to expand...
Click to collapse
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.
2k73 said:
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.
Click to expand...
Click to collapse
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.
REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
PizzaMaster said:
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.
Click to expand...
Click to collapse
Hey so i spent forever trying ro find a root that would work on this. Or a custom ROM anything really. Try going into McAfee Security, setting up an account, go to settings and disable the lock down device option. That was the problem for me at least McAfee was blocking any root from installing. From there i rooted my lucky with kingroot one click root. Hope this helps!
The Easiest Way To Root Your LG Lucky Without a PC
Easy way to install SuperSU on your LG Lucky
Just follow directions
Use KingRoot 4.5.0 app - google KingRoot apk all versions. Download and install apk.
Google replace kingroot with supersu. There will be a few sites popup, Mediafire is where the original .zip file is hosted. You can even search "how to replace/remove kingroot with supersu" here on XDA for more info.
Once you have downloaded the .zip file be sure to extract it to your INTERNAL sd, the script in the zip will not work from your external sd.
Open the extracted file and copy the mrw file to the internal storage, the path should look like /storage/emulated/0/mrw.
Now go to the play store, download and install Terminal Emulator. I use the one by Jack Palevich as it is only 551kb and easy to use.
Open the terminal emulator and type "su" in order to grant super user permission to the emulator,
On the next line type "/system/bin/sh - /storage/emulated/0/mrw/root.sh" and press enter.
Now the script will run and open up SuperSU automatically. Install binary when prompted with the "normal" option. Choose yes when it asks if you want to delete other superuser apps. (this removes kingroot).
Before rebooting phone, go into the settings of SuperSU and enable pro mode, change icon if you wish, enable survival mode, enable su during boot. I think you have to restart app at this point, can't remember as I did this months ago. Then restart the SuperSU app, go back into settings to Install SuperSU into system. Reboot phone,
When phone reboots, this is when Kingroot is finally uninstalled. Your phone will still be rooted with SuperSU. At this point you may wish to update SuperSU as this is version 2.46 and the newest version is 2.71 Beta. You can get the newest version of SuperSU from the thread here on XDA.
(thanks MrWolf for the script to make the change and thank you Chainfire for SuperSU, FlashFire, CF.lumen, etc...)
LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.
mikemc63 said:
LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.
Click to expand...
Click to collapse
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hi. Could you tell me how you installed supersu after rooting with kingroot? Thanks
Well I have root and supersu installed but it won't update binary. Any help out there? Thanks
Hey everybody. I did it!! Just root with kingroot 4.5 and replace kinguser with super sume. Worked great. All kingroot stuff is gone!! Ive rebooted 3 times to make sure and all is good.
Well if anyone is interested in looking at the source code, lg support has downloads available for nearly every phone they've ever made.
http://opensource.lge.com/osList/list?m=Mc001&s=Sc002
The file for the LGL16C is on page 2. Every thing seems to be listed alphabetically so it's easy to locate.
I still have my lucky and actually use it often although I no longer have it activated.
@ cecnwv,
Thanks for the link. Using Ares 11 and got "IP banned for 6 hours,try again later" after dbl tppng yellow icon. I did something wrong. Not at my PC. (unfortunately)
Thanks for any enlightenment,
michaeltheclyde
Two 10a LGL16C Tracfones, one free (recon from Tf) and one new $14.95 @ eBay from Best Buy, rooted with everything that has Google in the name frozen (TB) but no image to restore. (twrp)
Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.
Apache Thunder said:
Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.
Click to expand...
Click to collapse
Awesome, this worked for me too, though the issue wasn't exactly the same. When I got the phone it had already been rooted with Kingo at some point and I noticed after resetting it that I had similar problems (it may have had the issues before the factory reset too, I just didn't notice one way or the other). Anyway, I was getting slightly different misbehavior. No recents key, yes, but also no response from the Home key. Pull-down notifications bar was mostly working, but with no visible notifications and I couldn't press the Setup "gear" in top right. My volume buttons and Play Store were fine, though, but I'd noticed that when I tried further factory resets (from the menu, not via hard reset) that it wasn't "really" resetting, as any downloaded files/etc. remained on the phone. I'd tried freezing LGSetupWizard already, but as you noted, that doesn't fix it for whatever reason. Deleting altogether does. Yay. I do wonder what the hell is happening during the root or reset that triggers this problem, though. It behaves as if Setup Wizard was just never completed, so you remain "locked out" of most of the same functions that are unavailable during setup normally. Oh well.
Anyway, as old ten-dollars-or-less type phones go, this isn't the worst I've ever used by a long shot. Heck, it's arguably better than a few other slightly bigger/newer/pricier crap-phones out there! (Looking at you, ZTE Legacy/Quest...) FWIW, I had "ripped" all of the APKs from /system/app and /priv-app for some reason back when I first got this thing, so if they'd be of use to anyone I'll be happy to upload all or individual files. Hell, if anyone can tell me how to do a full ROM dump I'd be happy to do that too, because there's definitely still no official stock image available online that I could find a trace of. (Granted, I don't know if there'd be any way to utilize a non-official backup image anyway or turn it into a flashable KDZ, but that's not my point...)
Thank you, I got my lucky rooted! I'm wondering if anyone ever found any custom ROMs or recoveries for this device. It seems like this was never popular for any of that, but thought I'd ask. Thanks.
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