So, my sprint GS3 is rooted with SuperSu pro. The Android version that is on my phone is version 4.1.1 I never had a problem with the phone until one day it prompted me to upgrade the software and I accepted. The update was never successful. I have a picture attached that shows error message it gave. SuperSU pros' icon also doesn't show up anymore on my phone. My phone is still rooted because I can use Titanium back up pro. It has been acting up more and more ever since that first error message.
I've tried searching for similar problems on this website as well as on others but haven't found anything that's similar. I hope the picture helps and someone else who's experienced a similar problem can shed some light on mine because it's driving me crazy.
Have you verified Root, like with Root Checker ? It's Free in the Play Store. Have you tried to Update SU ?
It sounds like you were rooted and tried to get the 4.3 update. Luckily for you it didn't take. If you want 4.3, I would suggest you flash the Knox free version. Just follow the install instructions in the OP and it'll get you back rooted. If you want to stay on 4.1, try flashing super su update through cwm if it won't install from the play store.
Sent from my SPH-L710 using Tapatalk
Related
Hi all first post.
Spent the last 2 days trying to figure this out and need help.
Phone is AT&T Note 2 SGH-I317
4.1.2
Yesterday I received an OTA update for 4.1.2, though my phone was already updated to 4.1.2. Updated and lost root obviously. Anyway I thought no big deal I'll just use Chain Fires Odin method and re root.
I opened Odin ran through everything fine, Odin says I pass! I get the red Android, phone opens and no "super su" found. I opened "root checker" from Joe Krim, says I'm rooted. I really don't think I am so I open Titanium back up and TB says no root, as I figured.
So I'm thinking this latest OTA was a "fix" to stop rooting?
So I see on XDA Chain Fire has updated the CF Auto Root files for my particular phone. I try it again just prior to posting here with no luck.
I made sure to delete the older files from my "root" folder containing CF and Odin.
I also have tried this with "debugging" on and off.
Not sure what to try next.
Thanks
Looks like I got root up and running again.
I downloaded Super SU directly from the play store and everything seems like it running ok.
Thought I'd post in case anyone else has a similar issue.
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Capa1970 said:
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Click to expand...
Click to collapse
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
WearySky said:
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
Click to expand...
Click to collapse
I am not rooted.
Capa1970 said:
I am not rooted.
Click to expand...
Click to collapse
I wasn't able to find any way to get around Knox without rooting, but I may not have looked hard enough.
If you're willing to root first, CF Auto Root was super easy to do:
http://forum.xda-developers.com/showthread.php?t=1963790
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Capa1970 said:
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Click to expand...
Click to collapse
That *is* a Knox message, for sure.
So it looks like the Cyanogenmod team were not able to circumvent Knox for their CM installer. It's probably just a matter of time. Here is the full Knox notification:
"An application attempted to access system on your device without authorization. This attempt has been blocked. Updating your security policy may solve this problem. Deleting applications obtained from unauthorized sources may improve security."
There are three options at the bottom of the screen: Cancel, Update, and View Apps.
Update: I was able two days ago to use the Cyanogenmod Installer and I am now running CM!! First time for me to ever root and flash a Rom (I was an iPhone guy).
The phone is faster and smoother. I never liked the Touchwiz lag and most of the Touchwiz features worked inconsistently. The only thing that I miss is the camera. I have not found any bugs yet and so am very happy thus far.
I'm rooted stock 4.3, I hear the S3 has the 4.4.2 update? Is that true? What is the error in the attached screenshot mean as well? I'm connected to wifi and I get the error no matter what.
I also have another issue I'm curious about and rather than making a second post I'll ask that too.
I have the supersu app. My rooted apps completely detect root and work. I want to change from the supersu app to the Superuser app for personal preference. I get stuck at 'Making sure new su works'. Why? I also get this no matter what.
Screenshots of both issues attached.
The latest is 4.3. If you are rooted then you most likely have a custom recovery and that is why whatever OTA update you are trying to get is failing.
Hello everyone, please be patient with me as I am relatively new to modifying phones. However, I have spent a good portion of the past 1-2 weeks looking into this problem on XDA + google, and I am at the end of my rope.
Here is my problem (I'm sure you already know):
I have no current solution to installing a custom recovery on my phone. I really just want custom recovery to restore FULL backups via Nandroid or equivalent.
Here are my questions:
1) In download mode, Odin has no problem flashing an official image/firmware (tar.md5) to the phone. Is it possible to create my own image of my phone into one file and flash it via Odin to my phone when I would like to restore? I have a feeling that something in the phone checks the hash of the image (I'm sure that I'm not saying it right), and that, considering my image would be twice the size of the official, there would be no way to make my image pass using collisions or what not. However, this would probably be my first choice after safestrap (assuming that won't work), so let me know.
2) I have read that certain people with phones similar to mine (not my variant though) have successfully "swapped" the external and internal SD cards. If I remember correctly they just change a couple lines in void.fstab. If this could actually be done, I could easily restore a backup to the now external internal SD, then change the settings to reswap on reboot. I feel like this is too good to be true though, as I have not seen this as a solution to my specific problem online. Is this actually a suitable option?
3) Currently my phone model is not an officially recognized device which Safestrap will work on. However, I have read that it is possible to do on my model using the Safestrap version which corresponds to a close variant of my phone. Can this be done? Please let me know if you have any information on this.
4) I guess this would be the last resort. I'm pretty good at taking things apart, but even better I can put those things back together Is the internal "SD" really just an SD card deep inside the phone? Would it be possible to replace that card for the purpose of backing up?
Here are my phone specs:
-Samsung Galaxy S4 Mini (SCH-I435)
-The carrier is Verizon Wireless
-Android Version 4.4.2 (kitkat)
-Baseband Version I435VRUBOC1
-Kernel Version 3.4.0 [email protected] #1 Fri May 23 2014
-Build Number KOT49H.I435VRUBOC1
-Hardware Version I435.05
-Configuration version B13.SAM.SCHI435.0
-Needless to say, phone is rooted and has busybox + etc correctly installed.
Any help will be greatly, GREATLY appreciated -- even if that help is telling me that it isn't possible. I can't seem to give up on this.
Thanks,
Kurt
Help
Does anyone have any advice on this? I would REALLY appreciate it. Thanks again.
-Kurt
I'm also interested on this. Thanks for your efforts
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Kannz2 said:
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Click to expand...
Click to collapse
How did you switch it over to SuperSU? I tried, but when it tried updating the root binaries it couldn't continue because of KNOX, so I was stuck with Kingoroot's.
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Kannz2 said:
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Click to expand...
Click to collapse
I tried it with the free version they linked to and it de-rooted it, so maybe I'll try later when I have enough Opinion Rewards credit to get the pro version. That or it doesn't work on this phone with Kingoroot. (The Google Play description says it should do Kingoroot though.)
Did you download the correct version? The one off the kingroot site doesn't work for me. It just deroots. I still have root on both of my s4mini Verizon phones. Try this link to get a working one.HERE scroll down a bit and the different versions are there. Try each one starting with 4.5. Also remember to restart after you root with kingroot and install super sume after the restart.
I just had to re-image my phone, so I did it according to your directions. (Though with the free version still of super sume) and it worked, although it won't update to the newest root binaries. It fails when I try. Did you have this issue? Other than that, SuperSU works.
I updated using "normal" and it worked fine for me. Glad su works at least. also for one phone I did a full unroot factory reset and then I reflashed a tar with Odin. Did the normal root with kingroot 4.5. Restarted tried a few root things like no frills cpu thing then installed super sume pro. Did stage 1. An 2 then supersu started up automatically it asks to update (I think net connection is needed) *do update "normal" because there isnt any recovery. Uninstalled kingroot like supersume says. Did a few root things then restarted. (Checked for superuser after reboot and it stayed)
Ok so I have the gt-i9195 s4 mini. It was rooted but I needed to update it so I decided to un root it. With the root installed I couldn't update I just got a notification saying it was modified :/ So basically after I un rooted it I still couldn't update. After finding out I still couldn't update I factory reset it. Even after that I couldn't update. I didn't want to f*** it up any more so decided I wouldn't update it and just leave it. All was going well I set it up fine but then I go to download an app but I can't sign in to the play store because it can't establish a connection. I google a fix and followed multiple guides but none have worked. Is my phone fixable? If anyone knows how I can fix this and update it to the latest update please tell me Thanks
Zuthrane said:
Ok so I have the gt-i9195 s4 mini. It was rooted but I needed to update it so I decided to un root it. With the root installed I couldn't update I just got a notification saying it was modified :/ So basically after I un rooted it I still couldn't update. After finding out I still couldn't update I factory reset it. Even after that I couldn't update. I didn't want to f*** it up any more so decided I wouldn't update it and just leave it. All was going well I set it up fine but then I go to download an app but I can't sign in to the play store because it can't establish a connection. I google a fix and followed multiple guides but none have worked. Is my phone fixable? If anyone knows how I can fix this and update it to the latest update please tell me Thanks
Click to expand...
Click to collapse
download the rom and flash it by odin thats it
Zuthrane said:
Ok so I have the gt-i9195 s4 mini. It was rooted but I needed to update it so I decided to un root it. With the root installed I couldn't update I just got a notification saying it was modified :/ So basically after I un rooted it I still couldn't update. After finding out I still couldn't update I factory reset it. Even after that I couldn't update. I didn't want to f*** it up any more so decided I wouldn't update it and just leave it. All was going well I set it up fine but then I go to download an app but I can't sign in to the play store because it can't establish a connection. I google a fix and followed multiple guides but none have worked. Is my phone fixable? If anyone knows how I can fix this and update it to the latest update please tell me Thanks
Click to expand...
Click to collapse
Download stock rom from sammobile and flash it