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
Related
Is there a way to remove the "Custom" padlock message while the phone reboots from an mj5 build? I am unrooted and still continue to receive this, padlock, need to exchange phone at best buy any suggestions?
Fidelio_o said:
Is there a way to remove the "Custom" padlock message while the phone reboots from an mj5 build? I am unrooted and still continue to receive this, padlock, need to exchange phone at best buy any suggestions?
Click to expand...
Click to collapse
Re-root with Kingo then unroot with SuperSU. (Full unroot in the settings menu) After you restart the padlock should be gone. You may need to restart a second time so the system can switch back to Official status. I've done it twice now and it worked both times.
archie87 said:
Re-root with Kingo then unroot with SuperSU. (Full unroot in the settings menu) After you restart the padlock should be gone. You may need to restart a second time so the system can switch back to Official status. I've done it twice now and it worked both times.
Click to expand...
Click to collapse
Going to give it a shot.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Didn't work, try it like 5 times. no go.
Fidelio_o said:
Didn't work, try it like 5 times. no go.
Click to expand...
Click to collapse
Hmm strange. I must have gotten lucky.
you will have to use this and do a full install so it shows its not custom
http://forum.xda-developers.com/showthread.php?t=2559715
Download Wanam Xposed from the market. There's a hack in there to prevent the dreaded padlock
Sent from my SAMSUNG-SM-N900A using xda premium
Yup wanam solves it easily. First get Xposed framework, then install wanam, then in the security hack section in wanam, choose fake system status, reboot.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Bruce0750 said:
Yup wanam solves it easily. First get Xposed framework, then install wanam, then in the security hack section in wanam, choose fake system status, reboot.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
What IF they do a factory reset on the phone.....will this not just wipe the wanam exposed settings and BAM!!! the padlock will back and look even more like you messed up your phone?
i got my exchanged and had this same problem, they went through the phone scrupulously trying to find something that pointed to me tampering. they attempted to do a factory reset but with the state that i left my phone they could not even attempt that. but they tried, which will make your solution a Big Hell No once the reset brings that padlock back....they wont even talk to you anymore.
Bruce0750 said:
Yup wanam solves it easily. First get Xposed framework, then install wanam, then in the security hack section in wanam, choose fake system status, reboot.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Didn't work for me. Padlock still there at start up.
edessa said:
Didn't work for me. Padlock still there at start up.
Click to expand...
Click to collapse
how did you reboot your phone? you have to use wanam's reboot option to do so, just so wanam can update things to the system. if you reboot by other means, especially by holding the power bottom and select reboot, it won't get ride of the pad lock.
We'll that explains it. In the mean time stupid AT&T updated my phone when I wasn't looking. I am now put to MJ5. I guess I can try to root with kingo.
Edessa Kingo will root MJ5. Im on MJ5 and rooted with Kingo. You may have to run program 5to6 times but it works
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I got it to work by rooting and deleting busybox from system/bin and system/xbin. Which survives even after a factory reset. Was able to exchange the phone no problem after using full unroot from within SuPro. No padlock.
Sent from my SAMSUNG-SM-N900A using Tapatalk
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
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
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
After a while, I finaly could get root acces to my S5 g900a with base band NG3. Im trying to launch SuperSU and it says me to update binary code or number, something like that. When Is updating it, the app ask me for disable Samsung KNOX. After hitting "OK" it says me that it was impossible to disable.
I think thats why i cant use FlashFire to upgrade to Lollipop with an OTA. Can someone tell me how to do all of this? Thanx
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
I used titanium backup and uninstalled everything related to Knox without any issues, then I used flash fire to update to the pre rooted 5.0
darthmalus said:
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
I used titanium backup and uninstalled everything related to Knox without any issues, then I used flash fire to update to the pre rooted 5.0
Click to expand...
Click to collapse
@darthmalus I used another app similar app to delete everything with "KNOX" on it and I could get rid of the annoying Warning message, BUT i cant still update the binary from SuperSU (it says that the update failed) nor use FlashFire (it says that im not using SuperSU or im not rooted but i am)
Hmm that is strange im using Super SU and its updated just fine for me, sorry bruh i cant be of more help.
Just open super su ...update binary chose normal recovery not custom.it will say install success after that rebot and open super su now it will desable knox...
Sent from my SAMSUNG-SM-G900A
leoishwor10 said:
Just open super su ...update binary chose normal recovery not custom.it will say install success after that rebot and open super su now it will desable knox...
Sent from my SAMSUNG-SM-G900A
Click to expand...
Click to collapse
I did that, didnt work