Develop Bugs

Has anyone lost root access (temporarily) after installing latest 2.2 roms?

I installed a rom that was based off the released 2.2 that was released on Friday. I had root already and everything worked fine no problem. I flashed the latest radios and wimax and really nothing else. Well today I went to use Titanium Backup and it wouldn't run; just got a black screen. got the FC message. I then tried to use QuickBoot to reboot and that also didn't do anything. I manually powered off and rebooted and still the same actions from both apps. I then tried Wifi tether and that wouldn't start the sharing. Said that it was unable to Start. I think at that point my root access wasn't working properly. I looked at the Superuser permission app and it looked ok. I then tried another app that required root called Ad-Block and it said that it couldn't get root access.
The only way to get the apps working again was to flash the same rom I flashed on Friday. All apps are working fine after the re-flash.
Anyone else have this?

unknown_owner said:
I installed a rom that was based off the released 2.2 that was released on Friday. I had root already and everything worked fine no problem. I flashed the latest radios and wimax and really nothing else. Well today I went to use Titanium Backup and it wouldn't run; just got a black screen. got the FC message. I then tried to use QuickBoot to reboot and that also didn't do anything. I manually powered off and rebooted and still the same actions from both apps. I then tried Wifi tether and that wouldn't start the sharing. Said that it was unable to Start. I think at that point my root access wasn't working properly. I looked at the Superuser permission app and it looked ok. I then tried another app that required root called Ad-Block and it said that it couldn't get root access.
The only way to get the apps working again was to flash the same rom I flashed on Friday.
Anyone else have this?
Click to expand...
Click to collapse
That is possible. I had the same issues. To get the ad-free host files in, I had to do it in recovery mode and push the files which is like having the nand lock. I try to do some programs that require root and it reboots the phone.

Cyanogenmod Installer

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.

[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)

[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!

In SuperSU, try the clean-up for reinstallation option.

DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?

Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.

[Q] Tried rooting using Towelroot and chainfire but no joy

Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled

tried another method
Also tried using the casual method but that also failed with the error "Unsupported device" here is the url for the log file:http://pastebin.com/vZRvYH3g
I followed the follwowing thread:
http://forum.xda-developers.com/showthread.php?t=2189536
amti366 said:
Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled
Click to expand...
Click to collapse

After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.

DocHoliday77 said:
After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.
Click to expand...
Click to collapse
Hi Doc, I was able to follow one of your other treads at "http://forum.xda-developers.com/galaxy-s3-att/help/att-bricked-s3-help-please-t2817566/page2" and install TWRP. I think my issue was that the firmware had got upgraded to the NE4 and I was not flashing the correct bootloaders.
I do have one more question and I am not sure if it is a ROM related issue or a phone setting. I will understand if you think I should ask in the ROM thread. I flashed CM11 on the phone after installing TWRP and rooting with superSu. I noticed that the led buttons on the bottom of the phone are disabled(the back and the setting buttons) do you know if this is a changeable setting(pic attached)? I would hate to loose the screen-space at the bottom to the buttons and even though that's standard Kitkat layout I wont mind being able to use the phone led buttons to go back and change settings.
I installled the follwoing version of cm11: cm-11-20140805-SNAPSHOT-M9-d2lte.zip from (http://download.cyanogenmod.org/?device=d2lte)
Thanks for your help and guidance.
Matt

Im not sure about that one. I don't use CM so im not very familiar with all of its different settings. Someone else may have the answer for you though. If not, then ask in the rom thread like you mentioned.

root and tether, that's all i want

can anyone point me to some directions please. i'm a long haul trucker. so i don't keep up on this technology anymore. i've already spent half the night trying to root my sprint note 2 running 4.4.2. 3 different odins were all successful. but the actual supersu is non functioning.
i don't have nor really want to spend countless hours on google trying to do one root method after another. i just want to keep the stock software, root the darn thing and hopefully get wifi tether.
anyone, please????
p.s. it's been months since i've done this. and the phone has been deactivated till now, after 12 months. so i have no idea what bootloader i even have. i think it's either cwm or twrp. not sure. i'm way behind the curve in remembering the procedure.

You posted this in the wrong area..

What happened to our moderators? This is the second thread here that does not belong. If I was to do something like this they would be all over me like stink on sh!t.
To root your phone use cf auto root. Since your on stock rom you have to use a hotspot app from play store. There is a mod to make stock hotspot work but not for the stock rom.
Also next time you have a question please ask in q&a not development.
Sent from my SPH-L900 using XDA Premium 4 mobile app

personally, I prefer the Sprint Note 2 Toolkit. I won't install SuperUser or SUSuperUser, but your phone will be rooted. You can then just download SuperUser from Google Play. If you can use Odin, you should everything set. It's just a menu driven system. Just make sure you download the Note2 version. I recently goofed and did the Galaxy S3. Needless it didn't work, but I just odn the stock rom and tried again.
As for tethering, that'll depend on your ROM. Some roms may have it already incorporated, but those are more the AOSP. There are some stock baised that it as well. If you want WiFi and those are not working, you can use WiFi Tether Router from Google Play. It costs a few dollars; If memory serves me well, it was between three and four dollars. I use it all the time.and on both AOSP and TW roms. You may need BusyBox installed, but if you're rooted, you should have it anyway. Very useful tool.

that toolkit don't seem to do anything as far as root goes. unless it's in the paid version.
i think i got root finally working. busybox finally installed. knox is finally disabled.
tried the wifi tether router. it keeps asking for supersu permission. so that don't seem to work. least not on 4.4 anyways.
any other suggestions. i've got the trevemod but it's not working either. although i think it's an old outdated version. 3.3 i think it is. all i been able to find on google so far.

snowwy66 said:
that toolkit don't seem to do anything as far as root goes. unless it's in the paid version.
i think i got root finally working. busybox finally installed. knox is finally disabled.
tried the wifi tether router. it keeps asking for supersu permission. so that don't seem to work. least not on 4.4 anyways.
any other suggestions. i've got the trevemod but it's not working either. although i think it's an old outdated version. 3.3 i think it is. all i been able to find on google so far.
Click to expand...
Click to collapse
Do you have a superSu or superuser app in your app drawer? If so open it and it will want you to update your binary do the normal install. If not open play store and install superSU. You have to have a superuser app to give other apps superuser permissions without it you wont get wifi tethering to work.

she's working now. supersu, busybox, and wifi router.
we would appear to be in business.
thanks for all the help guys/gals.

snowwy66 said:
that toolkit don't seem to do anything as far as root goes. unless it's in the paid version. ...
Click to expand...
Click to collapse
The free version is all I have used. I've used it about about three or four times. You just need to make sure to install the samsung drivers, which Toolkit has menu option for. Enable USB debugging. Select the correct correct for it to download whatever tar image is uses. Select a recovery you want, it downloads. Later, you actually select the option to root and install a recovery. Really, the process takes about ten to fifteen depending on your download speeds.
The paid version has extra features
Also, TrevEMod WiFi Tether does not work on 4.3 and above. He was never updated for it. WiFi Tether Router works, as you know. It's a slow to start and terminate. Every once in a while it looses interest to the clients, but that's not often. I'm running CM8 which is Andriod 4.4.4.