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
Related
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.
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.
Hi!
I rooted my galaxy s7 edge that had stock version of android 7 (nougat) on it using this tutorial: http://www.droidviews.com/install-twrp-root-galaxy-s7-and-s7-edge-on-nougat-g935fxxu1dplt/. Now when I open built-in camera app it shows me a black screen for few seconds and then it says "Camera has stopped" and it offers me to "Open app again" and "send feedback" And it keeps happening over and over again.
Lemma: The reason is rooting.
Proof: Camera app worked perfectly. After I rooted my phone it started to crash like I described above. Then I tried to force quit camera app and delete it's cache/data. It did not help. After that I wiped entire cache partition. Still no help. After that I wiped all partitions except system. That did not work either. Then I re-flashed unmodified original stock ROM. Then camera worked perfectly again. Then again I rooted my phone the using tutorial I linked above. And again exactly the same issue. Camera app show black screen for few seconds and then crashes with exact same error message. ∎
Does anyone know fix for that? And why it happens? Is it some kind of samsung's anti-root thing that prevent camera fromworking on rooted phones or what?
Update [SOLUTION]:
In case someone else has same problem.
My solution was to skip restarts in TWRP steps. No restart between format and installing packages. Restart once when everything in TWRP part is done.
Root doesn't break your camera
I just Rooted my G935F that had Nougat as official firmware and had zero problems with the camera.
Sent from my SM-G935F using Tapatalk
I have international version of samsug with exynos CPU. Maybe this changes anything?
Root doesn't break your camera
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
I downloaded original firmware from here: https://www.sammobile.com/firmwares/database/SM-G935F/ (I chose baltic (only 1 occurrence in the table))
Maybe that specific tutorial I linked is bad one? Could anyone check that?
Rooted my G935F and no problems here for me.
I suggest you follow the tutorial here on xda and try again.
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
sysctl said:
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
Click to expand...
Click to collapse
A simple search here you'll find all you need. You are the only person I've ever read of that had camera problems like you've stated after Root. Again rooting won't break your camera.
I've Odin to stock literally hundreds of times testing Rom/Mods/themes as a tester for several teams from my s3 up to and including my G935F.
I've also flashed every Rom available for the G935F and the only ones with camera problems are the Lineage or AOSP Roms which more than likely are kernel related. Start here https://forum.xda-developers.com/announcement.php?a=81
Then this
Here's one
https://forum.xda-developers.com/showthread.php?t=3489011
sysctl said:
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Again rooting won't break your camera.
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Ok here is what you need to do.
Download a logcat app and get a logcat of it forceclosing.
I can't magically look in your device and see what, if anything is wrong.
As far as you saying you've searched well if you really did you would've found several tutorials.
How do I know?? Because I've used them myself.
It took me less than 5 minutes to root my new G935F using the TWRP Guide here on XDA
You seem to be the only one in hundreds that's claiming root broke your camera.
Provide a logcat in the Q&A and maybe a dev can help you.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Sent from my SM-G935F using Tapatalk
You could try to reset your settings
Same issue on smg935w8 lost camera and screen brightness. Also can't mount micro sd... we're you able to fix? I thought it was a bad root then I re flashed and the issue came back...twrp 3.1.0 supersu 2.79 and no verity 5.1
---------- Post added at 10:15 PM ---------- Previous post was at 09:50 PM ----------
im re flashing stock and tomorrow ill redo twrp and super su and skip dm verity patch think that might be the issue as it worked before for me last week and i then messed up by turning dev mode off and disabling oem and when i reflashed after that i have been flashing the dm verity patch....
give that a try if your still having issues
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Gray.Fox said:
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Click to expand...
Click to collapse
Thanks I've tried clearing cache for everything no luck. I originally thought it was because I might have deleted a system app with titanium but when I reflashed it all (firmware,tarp,supersu,no small verity disable 5.1) I still had the issue.
Lastnight I wiped and flashed the entire firmware. Everything works. Tonight I'm goi g to try and only flash twrp then supersu as I only want root. Hopefully that fixes my issues.
OP have your issues been resolved?
I'll let you know once I get it working on mine and we'll get you sorted out. I believe it's something with the steps or order as I had root fine for a day then had to reflash due to messing around and didn't do it my original way and that caused my issues.
flashed twrp 3.1.0 from odin with auto reboot off.
then booted to twrp. swiped right to mount system,
wipe data(format data) type yes.
mount microsd as mtp copy supersu 2.79 over if its not already on you microsd card.
else just install it from zip
cleared cache/delvik
rebooted to system
log in and setup everything and restore
camera and auto brightness...stilll doesnt work.
ok so after multiple tries to fix this (flash stock) everything works,, root and it breaks tried clearing all cache in system and twrp no difference... then i loaded phone info and used the secret codes to find out that my camera firmware is not installed....so im trying Flashfire to reflash the AP only while injecting supersu and maintaining root.... it is just booting up.....and OMG!!!!it works!!!!
so....for some reason...firmware was corrupting..... no clue why tired multiple methods and nothing... and im not a noob either.....
what finallllllllly worked was.... flash your rom and get root how you would normally. camera/auto brightness/and mounting usb doesnt work....boot to twrp. get your ap md5 file on your internal storage
reboot to system,. get flashfire from playstore or chainfires website
install and then click the + select firmware and select the tar file
only install system....uncheck boot and cp
then in the everroot select injject supersu, preserve recovery
and flash.... it will start flshing and boot to syteem once done..
everything is working nice
finalllyyyy!!!!
hope this can atleast help OP
no clue why i was losing firmware on the flashes
@unit68 Tnx for sharing. This time I got camera and brightness adjustment work out of box. But if in any point of time I happen to need your tutorial, I'll give it a try and let you know.
I am not sure if it is by chance or not but what I did differently this time was:
1) I paid attention to step where it asked to disable auto reboot (can anyone explain why?)
Previously I thought it shouldnt matter so I kept auto reboot for convenience.
2) I did format data, install no-verity-opt-encrypt-5.0 and SuperSU-v2.79-201612051815 and wipe dalvik cache with out rebooting between (Anyone know if that matters?).
Previously I had done it: format - reboot - install no enc - wipe dalvik cache- reboot - install super su - wipe dalvik cache - reboot .
Now I did it format - intall no enc - install super su - wipe dalvik cache - reboot.
I'll see for few days if anything else comes up or if camera breaks down again. Btw @unit68 what happens when you try some bloatware remover that run with root access? Do you get rid of bloatware or not? I tried few of them such as no bloat for example. Some complain that uninstall failed some seem to uninstall the app but when they reload app the app is still there and it's also still in app menu. Just curious if you have the same same issue. And is it safe to delete apk file manually? Or would it cause phone to crash/boot loop? When I ran supersu it complained about knox and asked me to disable it but it never managed to (however root checker tells me I am root). Maybe knox is protecting bloatware? Any ideas?
Flash your able too get it working! It was soooo frustrating. So for Knox supersu asks to disable then seems to hang so I go about my business reopen supersu it'll ask again and then is successful.
To remove bloat I normally just go to titanium and remove the ones I don't want
No issues on that and all my apps that require root work fine (titanium,adaway, flashfire)
This time disabling knox worked too... It turned out that all 3 apps that I used were note able to remove bloatware. App you named worked and also ROM toolbox lite works.
Btw when I google bloatware, the lists are incomplete.... Do you happen to know list of apps that must not be uninstalled? I guess white list would be better idea than black list.
Is installing/uninstalling app same as removing/adding apk files? So that I could cut and paste everything expect file manager and launcher to usb memory stick and then start adding required apps back one by one?
ive seen some samsung debloating software around. i honestly just remove stuff based on manually debloating for last fewyears. if i dont know what theapp is for i google it to see if its ok to remove. normally i remove samsung knox, few other samsung apps, some google apps (music, games, videio), briefings some edge panels, live wallpaper, and carrier branding apps(for me rogers) stuff like that. if you are going to i recommend you do a backup first as it ccan mess up your phone if you uninstall an important app. . also once your do uninstall you need to reboot ... the paid version of titanium allows you to freeze applications so you can try that first before removing it.
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
ScreAmeR01 said:
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
Click to expand...
Click to collapse
Interesting..ill check that if I need to to Flash. I have 2.79 but maybe I grabbed an old version or a beta. Mine says 20161205 I think it may have been sr3
Edit _ just checked I grabbed sr0 the stable release from 20161215 not the sr3 beta
Maybe it was corrupt when I flashed
Hi there
I wanted to add Messenger to UPSM screen (Ultra power saving mode), so I've tried UPSM Manager and UPSM+. None of them worked on my Galaxy S5 however, after few tries almost all of my apps disappeared. There are a few left. System: Contacts, Text messages, Phone, Settings plus Google and Lockwatch. That's all. The rest disappeared.
On application manager in settings I can see all of them, most of them have status "disabled".
I've downloaded those two apps from here:
UPSM Manager - https://forum.xda-developers.com/showthread.php?t=2751785
UPSM+ - http://downloadapk.net/down_UPSM-ROOT.html
I've read that there is a very high probability that they won't work and that Google does not refund price in such case hence downloading .apk - could it be some kind of trojan from the 2nd link?
I've connected with adb console and
PHP:
pm list packages -d
shows 300+ packages as disabled.
PHP:
pm list packages -d | while read line ; do pm enable ${line#*:} ; done
fails with
PHP:
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from ...
I can't run su as it freezes adb shell - su is also disabled so I can't enable it nor reinstall (Failure [INSTALL_FAILED_INTERNAL_ERROR])
Any hint how to restore my phone? Right now it has less features than Nokia 3210...
So maybe I'll ask a different question. Is there a way in my current state to regain root access (via adb shell) and enable disabled apps?
Marooned_MB said:
So maybe I'll ask a different question. Is there a way in my current state to regain root access (via adb shell) and enable disabled apps?
Click to expand...
Click to collapse
Hi,
In order to get helped it is always useful to provide at the beginning some basic info like phone model, firmware ver , root, recovery (custom or stock) etc.
Easiest way when you messed up your phone would be just restore your nandroid backup but I assume that you didn't make one, did you?
If not, easiest way IMO to regain root is just flashing CF-autoroot or if you have a custom recovery supersu zip file.
I wrote in Galaxy S5 forum so
Anyway: Samsung Galaxy S5 (SM-G900F), Android 5.0, G900FXXU1BOJ1, stock os, rooted
Haven't heard of nandroid before. I had titanium backup, but that's just apps I assume and they are still present on the phone, just disabled.
I haven't heard of CF-autoroot neither, but after picking matching details I got to desktop.firmware.mobi/device:370/firmware:12219 (I can't post urls with <10 posts). I'll have to read what to do with it without breaking a phone even more.
Marooned_MB said:
I wrote in Galaxy S5 forum so
Anyway: Samsung Galaxy S5 (SM-G900F), Android 5.0, G900FXXU1BOJ1, stock os, rooted
Haven't heard of nandroid before. I had titanium backup, but that's just apps I assume and they are still present on the phone, just disabled.
I haven't heard of CF-autoroot neither, but after picking matching details I got to desktop.firmware.mobi/device:370/firmware:12219 (I can't post urls with <10 posts). I'll have to read what to do with it without breaking a phone even more.
Click to expand...
Click to collapse
Here is the link to CF-autoroot for S5 variants:
https://forum.xda-developers.com/showthread.php?t=2696537
For applying you need to be familiar with using odin pc software. Be aware that this will trigger KNOX flag if yours is still 0x0.
By the way, how did you root your device initially?
KNOX was set when I initially enable root. To be honest, I can't recall which software I used, but it just worked without any problems. I was more than a year ago. Maybe it was CF but I just don't remember the name?
Anyway, I've generated image via CF-autoroot but it fails:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and now phone says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" :-/
Many40 said:
Here is the link to CF-autoroot for S5 variants:
https://forum.xda-developers.com/showthread.php?t=2696537
Click to expand...
Click to collapse
That one succeed. There is a high probability I've used that one upon first root.
Anyway, it succeed but adb shell and then su still freezes. Nothing changed. Still no root I guess.
Marooned_MB said:
That one succeed. There is a high probability I've used that one upon first root.
Anyway, it succeed but adb shell and then su still freezes. Nothing changed. Still no root I guess.
Click to expand...
Click to collapse
Hmm, so you still can't enable any disabled apps? I am afraid that you may need to try factory reset and if this doesn't help then re-flash complete firmware with full wipe. Before I would make backup of all useful staff what is still working and available in your phone.
Edit: did you read whole app thread? There are a few solutions/workarounds which helped some users with their issues but not sure if it is applicable to your problem,
Many40 said:
Hmm, so you still can't enable any disabled apps?
Click to expand...
Click to collapse
Yes, exactly the same access denied error as mentioned in the 1st post. Like nothing changed at all.
Many40 said:
Before I would make backup of all useful staff what is still working and available in your phone.
Click to expand...
Click to collapse
I've downloaded all files (available without root) from sd card and internal memory.
Many40 said:
did you read whole app thread? There are a few solutions/workarounds which helped some users with their issues but not sure if it is applicable to your problem,
Click to expand...
Click to collapse
Nope, I will then. At least I'll try (157 pages!)
Thanks for your help
Many40 said:
I am afraid that you may need to try factory reset
Click to expand...
Click to collapse
There is a button "delete everything" but it does not work. Nothing happens when I click it. So the next step is to reflash firmware? That seems like a bit over my knowledge at the moment :/
Also, I assume there is no way to backup sms/mms - not able to install any backup soft and no root for adb:
PHP:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
adb: error: failed to copy '/data/data/com.android.providers.telephony/databases/mmssms.db' to '.\mmssms.db': remote Permission denied
I'll try from recovery menu.
Ok, so it worked from recovery menu. Data are wiped, phone install some german bloatware and it's like when I first bought it. As I suspected, despite Google backup enabled, it does not work. No apps are being installed. I have to recreate every single app with it's data. That's a small disaster, ech..
Samsung backup restored some sms/mms but from February this year (heh).
Looks like all those automatic backup from Samsung and Google does not work at all and I should probably do some cyclic manual data dump. So why all those backup settings if it does nothing at all?
Anyway, thanks for your help.
Marooned_MB said:
Ok, so it worked from recovery menu. Data are wiped, phone install some german bloatware and it's like when I first bought it. As I suspected, despite Google backup enabled, it does not work. No apps are being installed. I have to recreate every single app with it's data. That's a small disaster, ech..
Samsung backup restored some sms/mms but from February this year (heh).
Looks like all those automatic backup from Samsung and Google does not work at all and I should probably do some cyclic manual data dump. So why all those backup settings if it does nothing at all?
Anyway, thanks for your help.
Click to expand...
Click to collapse
Sorry for that. What do you mean by saying "no apps installed" You wrote before that your apps (user and most of the system) have been disabled, not uninstalled by the UPSM.
Are all your disabled system apps still at the same state after factory reset?
You wrote german bloatware? It looks like you have German branded Lollipop 5.0 firmware installed. I would definitely move to Polish latest unbranded (XEO) Marsmallow 6.0.1 to clean up your phone or if you wish to have rooted and debloated stock-based firmware then this rom is a very good alternative:
https://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
Many40 said:
What do you mean by saying "no apps installed" You wrote before that your apps (user and most of the system) have been disabled, not uninstalled by the UPSM.
Are all your disabled system apps still at the same state after factory reset?
Click to expand...
Click to collapse
By saying "no apps installed" I meant that after factory reset (wipe from recovery menu) and signing into my google account, backup restore did not install anything. But I've done yet another reset, this time from options and this time I've set up google account on welcome wizard and.. it worked, google backup restored all 107 apps BUT with no settings (they claim that settings should be also restored), so I have all my apps, but with no settings, so like after fresh install. I'm recreating everything from scratch, one by one.
Many40 said:
You wrote german bloatware? It looks like you have German branded Lollipop 5.0 firmware installed. I would definitely move to Polish latest unbranded (XEO) Marsmallow 6.0.1 to clean up your phone or if you wish to have rooted and debloated stock-based firmware then this rom is a very good alternative:
https://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
Click to expand...
Click to collapse
Yup, phone was bought as (I'm not sure how to translate "powystawowy") refurbished, from shop exhibition(?), a bit cracked on corners, but 2x cheaper. Anyway, it was just a matter of uninstalling 5 German apps (with root of course).
I did not put any other firmware as the one from Samsung has some unique features like mentioned ultra power saving which I enjoy on long travels. I've read that custom roms does not support this or NFC and few others.
Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.
Alternatively is it possible to access the settings of this submenu through a different app or way?
hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen
True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages
Have you got any magisk module active?
estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP
Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:
Is there any risk involved concerning the encryption?
hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.
Stuck with the same issue. Did you manage to get it fixed somehow?
Actually the latest available oo update to 10.3.1 fixed it.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.
You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.
Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though