Hello,
I was rooted on 4.3 with Kingo. I never used the ISIS app before. But after I did the upgrade OTA to 4.4 I of course lost root. But the app is still saying i'm rooted..? Is this some kind of flag that it detected that I have been rooted before? I did some searching on how to enable it but I need root access again lol
Thank you,
reset phone!
burtonfamily101 said:
Hello,
I was rooted on 4.3 with Kingo. I never used the ISIS app before. But after I did the upgrade OTA to 4.4 I of course lost root. But the app is still saying i'm rooted..? Is this some kind of flag that it detected that I have been rooted before? I did some searching on how to enable it but I need root access again lol
Thank you,
Click to expand...
Click to collapse
You still have the superuser app installed probably because you didn't unroot before the update and it can't be uninstalled till we get root
Sent from my SAMSUNG-SM-N900A using Tapatalk
burtonfamily101 said:
Hello,
I was rooted on 4.3 with Kingo. I never used the ISIS app before. But after I did the upgrade OTA to 4.4 I of course lost root. But the app is still saying i'm rooted..? Is this some kind of flag that it detected that I have been rooted before? I did some searching on how to enable it but I need root access again lol
Thank you,
Click to expand...
Click to collapse
You are one of the many of us who simply didn't unroot before we either patched or received the OTA update.
We're waiting paitently for root.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Aw figured as such. By resetting the phone what's the best way to get everything back the way it was before I do a reset? Is there a simple backup app?
burtonfamily101 said:
Aw figured as such. By resetting the phone what's the best way to get everything back the way it was before I do a reset? Is there a simple backup app?
Click to expand...
Click to collapse
resetting wont fix it only way is to reroot then unroot to remove superuser so your stuck till we get root on 4.4.2
The only thing you can do is go to the Samsung Experience at Best Buy and ask them to flash the 4.4.2 ROM over what you have now, do a few factory resets after that and the Custom issue will resolve itself.
Same here, was hoping to find a solution. Want that $50
Sent from my SAMSUNG-SM-N900A using Tapatalk
Related
So,
I've had the phone for 2 months now. Did not root originally. Updated to AT&T's push of MJ5. Recently noticed that I get lockups/crashes periodically on stock apps. Like camera would start with black screen, or Alarms crash when they suppose to ring and would not ring. Decided to root but since on MJ5 used Kingo root. Not too worry about things passing on to China.
I was trying to get Isis to work and for some reason neither Xprivacy nor Isis root fixer work for me. Xprivacy did not do a thing - still got "you've got rooted phone". And Isis root fixer would let Isis work, but it would never complete setup. So I decided to go back to original unrooted stock.
Tried going with "First 3 Steps" in the Root-de-la-vega but running the EXE flash failed and I am back to rooted MJ5.
Should it work using Root-de-la-vega's exe to downgrade to MI9, so I can then use AT&T update to get MJ5? Or should I wait for next update and just accept it?
Do NOT use Root De La Vega if you are on MJ5. You will hard brick your phone.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
abalakersky said:
So,
I've had the phone for 2 months now. Did not root originally. Updated to AT&T's push of MJ5. Recently noticed that I get lockups/crashes periodically on stock apps. Like camera would start with black screen, or Alarms crash when they suppose to ring and would not ring. Decided to root but since on MJ5 used Kingo root. Not too worry about things passing on to China.
I was trying to get Isis to work and for some reason neither Xprivacy nor Isis root fixer work for me. Xprivacy did not do a thing - still got "you've got rooted phone". And Isis root fixer would let Isis work, but it would never complete setup. So I decided to go back to original unrooted stock.
Tried going with "First 3 Steps" in the Root-de-la-vega but running the EXE flash failed and I am back to rooted MJ5.
Should it work using Root-de-la-vega's exe to downgrade to MI9, so I can then use AT&T update to get MJ5? Or should I wait for next update and just accept it?
Click to expand...
Click to collapse
why dont you use the Factory reset option or enter recovery and wipe.
Hello,
I just got a Note 3 from ATT. I tried rooting the phone using the Kingo program, but each time the root fails with the message: "FAILED.. NOT SUPPORTED"
Has anyone experienced this? What can i do?
I am reading about the Root de la Vega, but I am afraid I am on MJ5 firmware, so I am not sure whether it is advisable to use it.
Are there other reversible rooting methods (ie, without tripping KNOX)?
cheers, MN
MannyNoela said:
Hello,
I just got a Note 3 from ATT. I tried rooting the phone using the Kingo program, but each time the root fails with the message: "FAILED.. NOT SUPPORTED"
Has anyone experienced this? What can i do?
I am reading about the Root de la Vega, but I am afraid I am on MJ5 firmware, so I am not sure whether it is advisable to use it.
Are there other reversible rooting methods (ie, without tripping KNOX)?
cheers, MN
Click to expand...
Click to collapse
I know when I did my phone it said failed. Did it two more times. Still said failed. The last time the phone had a disclaimer pop up, and the phone was rooted. So don't know how it worked but it worked. phone is rooted.
I was on mj5 and it worked fine. At the end of root it'll tell you failed if you don't grant it super user for a test but I didn't see any reason to allow it. Checked and I was rooted.
Sent from my XT907 using xda app-developers app
Thanks. I finally got it to work, by de-selecting (unchecking) the "developer option" that asks to "Verify apps via USB". Once I unchecked it, the process went succeeded. I guess this options was somehow preventing the super-user access. Anyhow, it worked, and I went ahead and rooted by wife's also.
Thanks for your responses - MN
mrkhigh said:
I was on mj5 and it worked fine. At the end of root it'll tell you failed if you don't grant it super user for a test but I didn't see any reason to allow it. Checked and I was rooted.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Both my build and baseband are MI9, can I use this method?
Yes.
Sent from my XT907 using xda app-developers app
Thanks I was getting the same Error and this Helped
Build NC2 Can I root?
I'm on build NC2 can I root (AT&T KitKat) using Kingo without voiding my warranty?
mrkhigh said:
Yes.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Won't void the warranty because it doesn't work on nc2
Sent from my SAMSUNG-SM-N900A using Tapatalk
I think I read somewhere that if the device has KitKat ... it will not root at all and at this time Kingo does not support kitkat for the GS Note 3
Gn3 on mj5
I have the GN3 on att
Rooted on mj5 using kingo worked fine
Unrooted using kingo.
Rooted again using kingo , still on mj5
Safestrap wiped data and cache, forgot to install rom.
Flashed stock MJ5 via Odin, phone boots fine. Flashed sec_csc.zip to fix the pen input error.
Performed several factory resets from device
No sim installed
USB debugging on
Unknown scources on
Verify apps off
USB verify apps off
Kingo root FAILS every time - (error notsupport)
What am I missing?
Which version of Kingo are you using? Did you flash the 28whatever.zip file after flashing the CSC file?
Try deleting the drivers and allowing them to reinstall
Sent from my SAMSUNG-SM-N900A using xda app-developers app
MannyNoela said:
Thanks. I finally got it to work, by de-selecting (unchecking) the "developer option" that asks to "Verify apps via USB". Once I unchecked it, the process went succeeded. I guess this options was somehow preventing the super-user access. Anyhow, it worked, and I went ahead and rooted by wife's also.
Thanks for your responses - MN
Click to expand...
Click to collapse
My option to uncheck Verify apps via debugger is greyed out an won't let me don anything with it. It does show up as uncheck, also the same in security. What should I try next?
Kingo root failed
Kingo root failed after remaining in the state of "Rooting" for a long time.
Mobile : Huawei HOL-U19.
Please help !!!
Kingo does not root kitkat you'll have to use towelroot.com. it works on the latest att update and most phones with kernel date July 2014 on down.
Sent from my XT907 using XDA Free mobile app
If one was to have SuperSu Pro with OTA survival mode, and update to KK would it work? Has anyone tried this?
Just a thought. :silly:
Don't quote me on this, but I'm pretty sure the update will still fail around 27%. There was something floating around here that said rooting the phone removes a file or something that the update looks for before allowing it to completely install. Obviously you have to be rooted to use SuperSU, so it most likely won't work.
We have people who managed to get it to update while rooted in survival mode it took root but left supersu in the system now unable to delete or use
Sent from my XT907 using xda app-developers app
yep, i did this and now have supersu in /system/app and su in /system/xbin, but root doesn't work and i can't get rid of them. the only real downside i've found so far is Isis Mobile wallet thinks the phone is rooted and doesn't work.. but i don't use Isis anyway.
Oh OK, I was just wondering. Thanks.
Sent from my SM-N900A using Tapatalk
Dankchild said:
Oh OK, I was just wondering. Thanks.
Sent from my SM-N900A using Tapatalk
Click to expand...
Click to collapse
yeah, it was worth a try for sure
Curious to see if anyone else has lost root after the latest supersu update? Rebooting did not change anything. I'm unable to use any root apps (xposed, root explorer, etc).
Any ideas?
Thx!
Sent from my XT1060 using Tapatalk
jco23 said:
Curious to see if anyone else has lost root after the latest supersu update? Rebooting did not change anything. I'm unable to use any root apps (xposed, root explorer, etc).
Any ideas?
Thx!
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
You should tell is if you are using a root exploit (and which one), what android version you are on, and whether or not you are BL-Unlocked.
I can tell you that my unlocked devices had no issues updating SuperSU, and root apps still work fine.
(I'm guessing you are locked since your signature says "Status 0")....but please confirm.
samwathegreat said:
You should tell is if you are using a root exploit (and which one), what android version you are on, and whether or not you are BL-Unlocked.
I can tell you that my unlocked devices had no issues updating SuperSU, and root apps still work fine.
(I'm guessing you are locked since your signature says "Status 0")....but please confirm.
Click to expand...
Click to collapse
sorry. correct locked. on 4.4.2 with root exploits.
but I got it back after installing other superuser apps.
Sent from my XT1060 using Tapatalk
jco23 said:
sorry. correct locked. on 4.4.2 with root exploits.
but I got it back after installing other superuser apps.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Oh, great! So problem solved, or are you seeking a solution to work with the most recent SuperSU?
I would rather use supersu, but so long as super user from click clockworkmod works, its all the sane for me.
Thx for the reply though.
I had to uninstall supersu, install super user, attempt to install it, reboot, make sure have root access via root explorer, install xposed, install adaway, soft reboot.
Sent from my XT1060 using Tapatalk
I installed 3.75 B03 safestrap on my S5A from AT&T. After I backed up my stock rom, I noticed that Safestrap was disabled and I lost my root on my phone. Does anyone know what might of happened? I have no custom roms or that sort of thing on my device. Please keep in mind that I just switched from IOS to Android a few weeks ago and am trying to learn everything via google. Thanks for any input on this matter.
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Rakuu said:
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
citron2k1 said:
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
Click to expand...
Click to collapse
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Rakuu said:
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
citron2k1 said:
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
Click to expand...
Click to collapse
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Rakuu said:
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, I did allow root checker root access. Sorry I missed that question. Further, everything ran smoothly with busybox. I'll just keep an eye on it. I hardly ever have to reboot my phone. Its just a minor hiccup that I have to deal with for now. Thanks for your help in this matter.