hello.
I have rooted my phone for some time with chainfire super user.
I started facing blue screen problems and random restarts now. thought maybe there is some hardware faults. started SU app and have choosed full unroot and problem have disappeared for some time.
What have happened and why?
firmware 4.4.2.
Currently i updated software through kies (nj1 update).
so far so good. no bluescreen for now.
update.. still getting randoms reboots... what is causing them?
I also had random reboots after I rooted. Though I don't think the super user app caused it. It happened only after I installed viper4android.
I changed roms since then and no problem.
Maybe you installed an app that causes it. Only thing I can suggest is, either change roms, or reinstall stock rom and root again
Did you delete Knox-related apps from /system?
no. i didn't delete them... should I? there were nothing mentioned about file delete in rooting manual so i did nothing.
Should I delete every file that contains word knox or any concrete files?
After I updated phone by kies, rooted again, data format couple times + dalvik cache clear, problem seems to disappear. for half day so far so good, no reboot.
to change rom will be next thing i will do if reboots reappear
Knox can cause problems on rooted phones. That's partly why you don't find Knox in ROMs based off stock. So yes, you should remove the Knox apps in /system.
just remembered... when I launched SU app it asked me do i want to disable knox. i choose yes.
is it enough for removing knox or it is necessary run for example DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0.zip
p.s. sadly i can't install busybox. after i click install it shows "checking system" forever
Choosing yes was the right answer, but while SuperSU does disable Knox, I'm inclined to believe it's only so that SuperSU can properly function and install the su binary and doubt it's permanent. However, I never tested this, as I delete Knox apps regardless.
Related
Ive got a weird issue that I cant seem to get around and I wanted to see if anyone else has had this problem.
I got a replacement phone from Verizon last week. It came preinstalled with JB and since we have Towelroot now, I let it take the OTA update.
I rooted with Towelroot and when I went to install SuperSU, it tells me Knox is active and asks me to disable and I say yes. At that point, the phone just sits there and grinds on disabling Knox. Ive let it sit an hour and it still just sits there grinding on Knox. Its never finished disabling Knox the first time and Ive flashed the phone back to factory and re-rooted 4 times now, Everytime its the same.
If I reboot after that and re-run SuperSU, it gives me the Knox warning again and when I say Okay, it immediately says Knox is disabled.
Check root and it shows Im rooted and behaves as such.
Then the problems start. I start getting stuff FCing all over the place. Ive tried to do a Fix Permissions from within BusyBox and that didnt seem to help at all. I unrooted and the problems went away. I rooted again and they came back and then I got stuck on the SuperSU Binary Needs To Be Updated loop where every time I update, it fails and closes SuperSU.
Has anyone had this issue and if so, did you figure out a way around it?
I had Same errors installing Chainfire's SuperSu Pro
But all is working good now.
it Gives root to what ever I grant access to, so no complaints here.
I Have seen other posts with same issue so I am sure CF is aware and working on the issue.
Also, I have not had any FC's since rooting and installing SuperSu
Thanks for the reply.. I think the FCs are due to Knox not being disabled properly but Im not sure.
Did Knox disable okay for you?
The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/
well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.
I used to be happy with my Galaxy S4 with stock 4.2.2 (rooted) but then I bought a Samsung Gear 2 Neo and I discovered I couldnt used it if I'm not in Android 4.3+ (with all the samsung garbage). Then I tried Ota update (i like the official way...) but no luck because of system modified (Triangle Away couldnt make it...), then I tried Samsung Kies and voila! Android 4.4.2 Kit kat (I9505XXUGNE8 and then rooted with Towelroot) , state of the art.... and now one restart every hour or more...
Sure is some kind of compatibility and I know I probably can "fix" it in many hard ways (and probably end up doing any of them):
- Factory reset + clean cache (I didnt do it when I updated because I like the official and the hard way... I want to keep my stuff...and now i cant go to recovery mode either...)
- Flash another ROM, etc..
But I would like to know why, even if i can't fix it (as in my job as programmer I like to find the bugs...).
I narrowed down the problem to probably related to the Gear 2 bluetooth connection with the Gear Manager, as it seems not happening if i disable the bluetooth (but not 100% sure, I havent been several days without bluetooth to test it because I like my new toy and dont want to be without it right after i got it...)
I learned about some apps that record the log just before the OS crashes so thats what i have now, a lot of error logs with not very good clues but seems the final error before the restart is always the same.
Here are the highlights (that i can see and that shows in all logs):
...
07-03 13:45:15.660 25043 25191 E AndroidRuntime: [email protected]*** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
07-03 13:45:15.660 25043 25191 E AndroidRuntime: java.lang.ArrayIndexOutOfBoundsException: length=14; index=-1
07-03 13:45:15.660 25043 25191 E AndroidRuntime: at com.android.server.am.ProcessList.computeNextPssTime(ProcessList.java:580)
...
07-03 13:45:15.971 25043 25191 E android.os.Debug: [email protected] > sdumpstate -k -t -z -d -o /data/log/dumpstate_sys_error
Where the hell is /data/log? I cant find it...
And here the full last log of a restart: pastebin.com slash 83p56NMN (I cant paste links...)
Please, any help or comment is appreciated.
Greetings,
Alex
I saw this in other thread:
Don´t disable KNOX messaging with SuperSU (might cause random system restarts or bootloop if you thereafter removing knox).
Simply remove all shown Knox stuff and you´r done!
I did that when SuperSu asked me.... could it be the cause? how can i undo that?
Anyone? Anything?
Also the log is full of MP-Decision Errors, if that could be related...
Sent from my GT-I9505 using XDA Free mobile app
It seems a common new bug not related to bluetooth or gear
I finally found other threads that are full of people with the same problem of random soft-boots after upgrading to 4.4.2 and having root or disabled KNOX or similar. I also had reboots without the gear connected so it seems its not the cause but just maybe another trigger of the problem...
I'll try all the suggestions in other threads until I can make the reboots stop....
More information about the problem related to Knox (STILL waiting to confirm if it is the source of the reboots...)
stuff_me said:
Yeah, first thing I made, was the same thing after towelroot. I installed supersu from play store and I let it to disable knox.
Is there any way to revert that from supersu? I would feel more comfortable in that way. I did install titanium backup and found bunch of knox apps and services, but the app doesn't show out of the box is it freezed or unfreezed? Besides, I don't even know is that what supersu did(did it freeze it or disable, or what)?
Should freezing and then unfreezing from TI backup work? And after that I can delete all knox related crap?
Click to expand...
Click to collapse
I made the same mistake but after reading some posts in this thread I could unfreeze the knox apps that SuperSu had frozen using Titanium Backup. Just check all apps that contains Knox in the name and you will see a couple of them frozen ( in my case "Knox Notification Manager" and "KnoxMigrationAgent")
Now I will see if the reboots stop and maybe I uninstall of the Knox apps (or maybe not...)
SOLUTION!!!
See my post in: http://forum.xda-developers.com/showpost.php?p=53896735&postcount=71
Everything of KNOX (2.0) must be deleted!!
Thanks for the info. For now by only unfreezing the knox that were frozen the restarts have stopped for some hours. I'll wait until the end of the day to see if it remains stable.
The knox apps are not bugging me so I prefer not to mess with them yet...
Are there more benefits for uninstall or erase them apart from the restart problem?
Sent from my GT-I9505 using XDA Free mobile app
10 hours without reboots after unfreezing the knox apps that were frozen by supersu. In my case it seems the only thing necessary
Sent from my GT-I9505 using XDA Free mobile app
Degghy said:
SOLUTION!!!
See my post in: http://forum.xda-developers.com/showpost.php?p=53896735&postcount=71
Everything of KNOX (2.0) must be deleted!!
Click to expand...
Click to collapse
I'd be not so imperative... I upgraded to 4.4.2, NF2, I DID NOT disabled anything of Knox, did not deleted it (simply: I'm not touching it) and I have no restarts since last 10 days (after update).
Secondly, you have rooted using CF-root which uses completely different mechanism (tripping Knox) than towelroot.
I have the Note 4 (SM-N910H), I've had mine rooted for 2 weeks and it kept randomly rebooting twice or so every 1-2 days, now I've removed the root and everything seems to be working fine with no reboots for 1 week. Most (I even think all of them) of the random reboots happened while the phone was idle (screen off).
I've rooted using the CF-Auto-Root via odin.
Anyone knows why the root was causing random reboots for me? I've tried with knox disabled and enabled and with both options I get the same reboots while the phone is idle, also I would like to mention that I don't have an SD card in my phone. I tried everything, Tried a recovery reset, tried a soft reset... It only happens when I root it.
Thanks.
Sometimes xposed module can be a culprit.
Sent from my SM-N910G using xda premium
It keeps rebooting mine so if i unroot it will solve the issue?
dr.ketan said:
Sometimes xposed module can be a culprit.
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Xposed sucks on a stock odex roms. I suggest you flash a new rom or deodex your stock rom.
the note4 i have atm was never rooted (efuse intact), but it also reboots randomly every few days, sometimes every few hours!
so i would say root is NOT the general cause!!
maybe, or perhaps root makes it worse, but it cant be the only reason!!
TML1504 said:
the note4 i have atm was never rooted (efuse intact), but it also reboots randomly every few days, sometimes every few hours!
so i would say root is NOT the general cause!!
maybe, or perhaps root makes it worse, but it cant be the only reason!!
Click to expand...
Click to collapse
In my case it's the issue, I've had mine un-rooted for 3 weeks now with no any random reboot, I rooted it yesterday using CF auto root just to test and it rebooted today while it was idle. I've never used any Xposed modules. It's also on stock rom and stock recovery.
menko2 said:
It keeps rebooting mine so if i unroot it will solve the issue?
Click to expand...
Click to collapse
I think it's worth a try to unroot and see if the problem is solved for you.
Thank you.
Do you know how to unroot?
The biggest problem is how to pass my apps and data without Titanium that needs root access..
menko2 said:
Thank you.
Do you know how to unroot?
The biggest problem is how to pass my apps and data without Titanium that needs root access..
Click to expand...
Click to collapse
Just flash the latest stock ROM from sam mobile (http://www.sammobile.com/firmwares/) for your exact model number and CSC using odin, no data or apps will be lost and root will be automatically removed after the process.
You can install "Phone INFO ★Samsung★" from play store to know what your exact model number and CSC, you can also type all the fields you get after you open it (except for your IMEI) and write them down here to me so I can give you a link of the stock ROM from sam mobile so you just download and flash via odin.
After rooting open SuperSu and choose never for the question to also disable Knox. Until now I didn't have any unexpected reboot.
Planet X said:
After rooting open SuperSu and choose never for the question to also disable Knox. Until now I didn't have any unexpected reboot.
Click to expand...
Click to collapse
I mentioned in my original post that I tried with both, knox disabled and enabled but with both options I had the same random reboots, no matter what I do, the same problem for me as long as I am rooted. Did you have random reboots before while you are rooted and now you fixed it somehow?
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
Root same way as you rooted marshmallow. Flash twrp, flash supersu 2.79. everything is the same. it will take a while to boot though be patient.
Flash TWRP in Odin
Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
no its not working......After install recovery stuck in Samsung Flashing logo....
TWRP is making the devices get stuck on Samsung logo....
I think what is happening is that when you install only the twrp the encryption of the device conflicts and leaves in bootoolp. When you install twrp and root , root already comes with a tool that takes out the encryption. But if you just want twrp, as was my case, you should, first of all, on your own twrp, wipe data and then flash no-verity-opt-encrypt.
Having root and no encryption sucks. Think I'll wait
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
sriszone said:
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
Click to expand...
Click to collapse
You can root but you have to disable encryption. Not a fan of that personally so I'll wait for another solution. If I lose my phone at least I'll have secure power up enabled. There is no bypassing that. There are too many FRP exploits on Youtube so having no encryption and simply a password isn't enough in my opinion.
---------- Post added at 10:29 PM ---------- Previous post was at 10:29 PM ----------
Mystero said:
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
Click to expand...
Click to collapse
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Galactus said:
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Click to expand...
Click to collapse
Hi, i cannot manage to unistall S Health, tried already two apps, after reboot app is still there and if i try to install older version i get corrupted file error.
guys please explain what is encryption and unencription here.... how can i disable ? can we flash this no-verity-opt-encrypt-5.0.zip
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
I got fully working root and TWRP on Nougat G935FXXU1DPLT.
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
Mystero said:
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
Click to expand...
Click to collapse
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
CuBz90 said:
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
Click to expand...
Click to collapse
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Mystero said:
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Click to expand...
Click to collapse
Try titanium. Backup the app first and then uninstall.
CuBz90 said:
Try titanium. Backup the app first and then uninstall.
Click to expand...
Click to collapse
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Mystero said:
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Click to expand...
Click to collapse
i have tried to remove the s health app with titanium but everytime i try to install vesrion 4.8 phone says that i can not install this app beacuse there is a package with the same name
what verison did you install before s health 5 and how did you install it.
and can anyone tell me how do i make lucky patcher to work properly