Just upgraded from the Incredible to the S3. Rooted, unlocked, and running Clean ROM. Wanted to play a movie on Flixster, but it detects root. I used to use OTA Rootkeeper to temp unroot, but it says it won't work on the S3 (I still tried, and confirmed that it doesn't).
Any suggestions?
Bramton1 said:
Just upgraded from the Incredible to the S3. Rooted, unlocked, and running Clean ROM. Wanted to play a movie on Flixster, but it detects root. I used to use OTA Rootkeeper to temp unroot, but it says it won't work on the S3 (I still tried, and confirmed that it doesn't).
Any suggestions?
Click to expand...
Click to collapse
I have attempted this multiple times as well and here is the basics, it does work, as I am running clean rom 5.0 with root and vodoo ota rootkeeper. I believe the trick is to ensure you temp unroot the device before accessing flixter application. So for instance if you happen to start the flixster app first, which I have a bad habbit of doing, you need to make sure to close out all running processes from flixster to ensure it doesnt detect, believe it is part of the initial startup process for the check, but unsure, either way have tried this on mine and was successful, so figured would try to help, hope it does.
I figured it out. You use SuperSu and disable SuperSu, then restart the phone.
Sent from my SCH-I535 using XDA Premium App
Related
has anyone else found that there phone is no longer rooted after the AT&T JH7 update??? I noticed that the USB tether is no longer on the phone and went to use Barnacle Wifi Legacy and it told me that it only worked on a rooted phone. I checked BusyBox and indeed, the phone is no longer rooted. It looks like I have to start over. Has anyone seen any problems with re-rooting, lag fix or anything else after the update??
GaryS1004 said:
has anyone else found that there phone is no longer rooted after the AT&T JH7 update??? I noticed that the USB tether is no longer on the phone and went to use Barnacle Wifi Legacy and it told me that it only worked on a rooted phone. I checked BusyBox and indeed, the phone is no longer rooted. It looks like I have to start over. Has anyone seen any problems with re-rooting, lag fix or anything else after the update??
Click to expand...
Click to collapse
Samsung kies did the update for me when i plugged the phone into the computer. After it updated, it also broke my root and added all the att crapware again. I re rooted with no problems, and removed the bloatware. Phone is working great. I havnt really noticed any difference.
GaryS1004 said:
has anyone else found that there phone is no longer rooted after the AT&T JH7 update??? I noticed that the USB tether is no longer on the phone and went to use Barnacle Wifi Legacy and it told me that it only worked on a rooted phone. I checked BusyBox and indeed, the phone is no longer rooted. It looks like I have to start over. Has anyone seen any problems with re-rooting, lag fix or anything else after the update??
Click to expand...
Click to collapse
How did you do the update? I did it fine and root wasn't removed.
AW794 said:
Samsung kies did the update for me when i plugged the phone into the computer. After it updated, it also broke my root and added all the att crapware again. I re rooted with no problems, and removed the bloatware. Phone is working great. I havnt really noticed any difference.
Click to expand...
Click to collapse
Has anyone updated with the Voodoo lagfix in place? I can always reflash the stock JF6 and then look for the update, but i am lazy.....
I updated through kies as well. Lost my root. used one click to root again and have had no issues.
I can't re-root! I want to re-root and install Unleash the Beast... I've downloaded it, renamed to update.zip... Put it in the internal SD, went into recovery and hit re-install packages and it no longer recognizes the update. I'm going nuts here trying to re-root... comes up... E:can't open /sdcard/update.zip (no such file or directory) Installation aborted ............... Grrrrrrrrrrrrrrrrr... Help here..
That's odd. I did the OTA update by going into the system menu and selecting check for updates (I never installed the Kies software). I got the failed update message but the version showed it was JH7 after the restart, I'm still rooted and the bloatware did not reappear.
Also I never changed from the stock rom, I just rooted to get rid of the bloat and be able to sideload. I suspect those that did flash a new rom may have replaced the bloatware when they re-flashed to stock?
Hope this is helpful info for someone.
Sent from my SAMSUNG-SGH-I897 using XDA App
JasonCL said:
That's odd. I did the OTA update by going into the system menu and selecting check for updates (I never installed the Kies software). I got the failed update message but the version showed it was JH7 after the restart, I'm still rooted and the bloatware did not reappear.
Also I never changed from the stock rom, I just rooted to get rid of the bloat and be able to sideload. I suspect those that did flash a new rom may have replaced the bloatware when they re-flashed to stock?
Hope this is helpful info for someone.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I too am running the stock rom and it still killed my root.
JasonCL said:
That's odd. I did the OTA update by going into the system menu and selecting check for updates (I never installed the Kies software). I got the failed update message but the version showed it was JH7 after the restart, I'm still rooted and the bloatware did not reappear.
Also I never changed from the stock rom, I just rooted to get rid of the bloat and be able to sideload. I suspect those that did flash a new rom may have replaced the bloatware when they re-flashed to stock?
Hope this is helpful info for someone.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Same exact thing happened to me; Still rooted; Also have the JH7 suffix. Very weird, but all in all there are no changes to my phone.
How do you tell if your phone is still rooted?
(Yeah, still new to Android.)
My phone would not update...50% only whether I do it or ATT sends me the Update...Wife updated fine but was not rooted because I could not get into recovery mode until the update....then rooted hes...I Odin mine back to stock was on the phone with ATT for 2 hours.....Getting new phone
Never mind I used mini k I e s and the install went fine on both phones
No issues anymore.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Shival said:
How do you tell if your phone is still rooted?
(Yeah, still new to Android.)
Click to expand...
Click to collapse
Open busybox, it will tell you.
Sent from my SAMSUNG-SGH-I897 using XDA App
JasonCL said:
Open busybox, it will tell you.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Wasn't sure how to just open Busybox so I just has Titanium Backup Reinstall it to make sure haha.
Thanks!
Is anyone else having problems getting jellybean its to install? It keeps failing I'm rooted running stock rom and have voodoo temp unroot while trying to install. Still no luck
DizzyFox said:
Is anyone else having problems getting jellybean its to install? It keeps failing I'm rooted running stock rom and have voodoo temp unroot while trying to install. Still no luck
Click to expand...
Click to collapse
If you froze, or removed any apps that are not normally removable if not rooted, the install will fail. Safestrap has been known to cause OTA failures in the past. Dont know if that is still an issue or not.
djousma said:
If you froze, or removed any apps that are not normally removable if not rooted, the install will fail. Safestrap has been known to cause OTA failures in the past. Dont know if that is still an issue or not.
Click to expand...
Click to collapse
OK nothing frozen or removed. But I do have safe strap is there anything I can do with it to make the its work. Like uninstall it?
open the app, choose uninstall recovery.
open settings/apps/manage and uninstall the app
check both internal and external SD cards for any Safestrap folders and delete them.
Action123 said:
open the app, choose uninstall recovery.
open settings/apps/manage and uninstall the app
check both internal and external SD cards for any Safestrap folders and delete them.
Click to expand...
Click to collapse
Thanks worked like a charm. Update completed root restored using ota root keeper entitlement check completed. Jellybean smooth as butter.
I've never used safe strap and I tried using OTA rootkeeper to temporarily unroot and it still won't update...
Sent from my DROID RAZR HD using xda app-developers app
Tyler2265 said:
I've never used safe strap and I tried using OTA rootkeeper to temporarily unroot and it still won't update...
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
did you update/remove any of the verizon supplied apps? If you froze them with TB, then just unfreeze them. If you have deleted any of them, then you will have to find the root thread here and startover installing ICS, and move forward with the updates from there.
I wanted to install the newest update but it keeps failing. I am stock rooted, used the root keeper app but still can not update. I also have all stock apps installed. I also unrooted and still can not update. Any suggestions?
chuck860 said:
I wanted to install the newest update but it keeps failing. I am stock rooted, used the root keeper app but still can not update. I also have all stock apps installed. I also unrooted and still can not update. Any suggestions?
Click to expand...
Click to collapse
Did you remove bloat?
All apk's must be there.
A FDR won't put them back.
My phone was stock, rooted, unlocked bootloader -> took upgrade with no issues at all.
chuck860 said:
I wanted to install the newest update but it keeps failing. I am stock rooted, used the root keeper app but still can not update. I also have all stock apps installed. I also unrooted and still can not update. Any suggestions?
Click to expand...
Click to collapse
Without knowing why, your best option is to download the HD utility and restore your phone to compete stock. There is something not passing the update check and if you aren't sure what the utility will get your phone where it needs to be.
Sent from my DROID RAZR HD using Xparent Purple Tapatalk 2
I have searched the forums and can't find anyone with this problem. (Although I am also having similar problems to others who took Verizon OTA to 4.3.)
I was rooted, using CWM/TWRP. I backed up my ROM, temporarily unrooted with OTA Rootkeeper, which actually worked. I got the OTA update to 4.3. Sadly, this was before word was out about all the problems. (The rootkeeper is what apparently worked because VZ pushed this update out several days ago and my prior rooted ROM would not accept the update.)
I initially got stuck on the yellow triangle "go to Verizon now" screen but managed to get past that. What is troubling me is this: When I open Super SU, I get the "binary needs to be updated. Continue?" I click "continue" but then it asks to update "normal" or "TWRP/CWM." If I click TWRP/CWM, my tries to boot into recovery but then just goes to the yellow triangle of death page again and I get stuck until I can trick past that screen again. If I click to update "normal" it tries to update but then I get "Installation failed!"
Anyone know the problem with updating the SU binary?
What is super weird, though, is that my Supermanager app is working just fine, even the root only functions such as superlauncher.
My App Quarantine application also works just fine and it is root only. But when I try to open Titanium Backup, it won't grant superuser permission. So, it seems my phone is still rooted but not really?
I also cannot boot into recovery either using hardware buttons or using ROM manager.
This is very frustrating for me.
Does anyone know how to figure out my rooted or not rooted issue?
Thanks for any help!
nessa23 said:
I have searched the forums and can't find anyone with this problem. (Although I am also having similar problems to others who took Verizon OTA to 4.3.)
I was rooted, using CWM/TWRP. I backed up my ROM, temporarily unrooted with OTA Rootkeeper, which actually worked. I got the OTA update to 4.3. Sadly, this was before word was out about all the problems. (The rootkeeper is what apparently worked because VZ pushed this update out several days ago and my prior rooted ROM would not accept the update.)
I initially got stuck on the yellow triangle "go to Verizon now" screen but managed to get past that. What is troubling me is this: When I open Super SU, I get the "binary needs to be updated. Continue?" I click "continue" but then it asks to update "normal" or "TWRP/CWM." If I click TWRP/CWM, my tries to boot into recovery but then just goes to the yellow triangle of death page again and I get stuck until I can trick past that screen again. If I click to update "normal" it tries to update but then I get "Installation failed!"
Anyone know the problem with updating the SU binary?
What is super weird, though, is that my Supermanager app is working just fine, even the root only functions such as superlauncher.
My App Quarantine application also works just fine and it is root only. But when I try to open Titanium Backup, it won't grant superuser permission. So, it seems my phone is still rooted but not really?
I also cannot boot into recovery either using hardware buttons or using ROM manager.
This is very frustrating for me.
Does anyone know how to figure out my rooted or not rooted issue?
Thanks for any help!
Click to expand...
Click to collapse
When you accepted the update, you're not supposed to do anything that has to do with CWM or TWRP. This is because the Knox bootloader has taken over.
Try rooting through the saferoot method and then use titanium backup again.
As for the binary, can't really answer that since I'm not on the Android 4.3 update (can't accept official updates because of my micro SIM card). Go to the official 4.3 discussion thread and then ask about this.
Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=2575661
Hello there
I am running a custom ROM on my Galaxy S8 and it is rooted using Magisk rather than SuperSU. SnapChat works fine with Magisk as it does not detect the root, however I've tried everything with the Barclays Mobile App but I just get stuck on the first screen and nothing happens afterwards.
At first it used to ask me to grant it root permissions and of course I did, but it has never actually worked.
I am not completely sure, but I have a feeling it has to do with the fact that my device is rooted.
Can someone please shed some light on this? I really need to get this application working as it is important for me. Do I have to go back to completely stock in order to use this application?
Thanks!
yes, it doesn't work on rooted devices. One of the ways that it tries to detect root is by trying to get root, as it happened in you case. By granting it root access, you marked your phone as rooted, and disabled the app. In case you were wondering, it has many other ways to detect root. It used to work with magisk hide, but I tried just today, and it seems that they can detect it too, as I can't use it anymore. By the way, your phone is flagged as rooted, and you will either have to do a factory reset to get it working, or call Barclays, but I think that there is no way to get it working. If you find out how to get it to work, please share it.
TarekElsakka said:
Hello there
I am running a custom ROM on my Galaxy S8 and it is rooted using Magisk rather than SuperSU. SnapChat works fine with Magisk as it does not detect the root, however I've tried everything with the Barclays Mobile App but I just get stuck on the first screen and nothing happens afterwards.
At first it used to ask me to grant it root permissions and of course I did, but it has never actually worked.
I am not completely sure, but I have a feeling it has to do with the fact that my device is rooted.
Can someone please shed some light on this? I really need to get this application working as it is important for me. Do I have to go back to completely stock in order to use this application?
Thanks!
Click to expand...
Click to collapse
Barclays app worked for when I was using magisk v14. Since update magisk v.15 barclays app stop working. If you can try to install magisk v.14
P.s. I was using magisk v14 and somehow magisk updated itself to v.15