[Q] KINGO Root for AT&T Note 3 - Part 2 - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?

war1957 said:
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
Click to expand...
Click to collapse
Yeah, it's odd. Doesn't work for me either. Even after multiple reboots. I'd love for someone to chime in for more details. I know this has been talked about somewhere, but the only answer I remember was selecting fake official status in Wanam and reboot a few times after that. After many reboots, it's still CUSTOM, but Knox and everything is 0x0. Thanks.

war1957 said:
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
Click to expand...
Click to collapse
That's really weird, because this worked fine for me. I didn't do anything differently though, are you sure you have Wanam enabled in the Xposed Framework? After you download a module you usually have to enable it. I would try unchecking and checking, rebooting in-between.

It's true. You have to enable that module within the Xposed App. Try a total shut down and not just a reboot as well.
Pull your battery. After that, the icon will go away. You also need to go look at your About Phone and see system status. Make sure it shows Official (It should). Good Luck and let us know....

When I removed the "Custom" icon from startup screen, it took more than one reboot cycle to go away.
The first reboot after applying the setting, there was still the "Custom" and unlocked lock. I thought nothing of it, since I didn't really care... But at some point after that, with no further action in Wanam, the "Custom" stopped showing on reboot.

I rooted again with the same method and custom miraculously vanished.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

LuckyColdJohnson said:
It's true. You have to enable that module within the Xposed App. Try a total shut down and not just a reboot as well.
Pull your battery. After that, the icon will go away. You also need to go look at your About Phone and see system status. Make sure it shows Official (It should). Good Luck and let us know....
Click to expand...
Click to collapse
Tahnks a bunch
After the *hard reset* it decided to work.
Happy customer now !! :laugh:

war1957 said:
Tahnks a bunch
After the *hard reset* it decided to work.
Happy customer now !! :laugh:
Click to expand...
Click to collapse
Glad to hear that, and thanks for hitting the thanks button. I'm glad we could help. Now, I'm going to give you your first thanks for replying back. Thanks again.

Related

[Q] Update, OTA/Kies with root?

I have rooted my GS4A with odin. but now i see there is a update for my phone out.
i am still on mf7, but got an update for HM2(nordic countries).
and i cant update with OTA or kies, ("unit have been changed"). could i just download the firmware from ammobile and flash it with odin? and hopefully nothing is lost?
if someone could give me a writeup i would appriciate it.. want to stay with stock roms but still rooted.
Anyone?
Sent from my GT-I9295 using XDA Premium 4 mobile app
I just did the update myself - I use Triangle Away to work past the detection and do the OTA update, but I had to use the advanced features in the paid version to get it to work. After update you have to re-root it the same way you did the first time. Note that super su might not be installed automatically again, so you might have to uninstall it and reinstall from the playstore after rooting to get it working.
The Triangle Away setting I had to use is "System modified workaround", and the instructions are right below the setting. You enable it, reboot, then disable it and do the update before rebooting. First time I had to try a couple of times, this time I enabled and rebooted, then started the download of the update, then disabled it before installing, and it worked first try.
Good luck!
Cederic said:
I just did the update myself - I use Triangle Away to work past the detection and do the OTA update, but I had to use the advanced features in the paid version to get it to work. After update you have to re-root it the same way you did the first time. Note that super su might not be installed automatically again, so you might have to uninstall it and reinstall from the playstore after rooting to get it working.
The Triangle Away setting I had to use is "System modified workaround", and the instructions are right below the setting. You enable it, reboot, then disable it and do the update before rebooting. First time I had to try a couple of times, this time I enabled and rebooted, then started the download of the update, then disabled it before installing, and it worked first try.
Good luck!
Click to expand...
Click to collapse
Hi thanks for your reply. i fiddled with triangle away all morning, got my status to official. but i couldnt get it to work.
here is what i`ve done:
ticked off "System modified workaround", rebooted and downloaded the firmware. but when i try to disable the "SMW" I get an error from triangle away as it could not access superuser su/root access.. so i have to wait till supersu is enabled again to gain access to triangle away to disable "SMW".
tried again and again, but everytime i get an error that says "could not update, try with kies or contact samsung".
buljo said:
Hi thanks for your reply. i fiddled with triangle away all morning, got my status to official. but i couldnt get it to work.
here is what i`ve done:
ticked off "System modified workaround", rebooted and downloaded the firmware. but when i try to disable the "SMW" I get an error from triangle away as it could not access superuser su/root access.. so i have to wait till supersu is enabled again to gain access to triangle away to disable "SMW".
tried again and again, but everytime i get an error that says "could not update, try with kies or contact samsung".
Click to expand...
Click to collapse
Yeah that's the problem I had when I got the first update. What I did the second time was...
Tick system modified workaround
Reboot
Start download of update while root is not available
Click hide or whatever it is, the download will move to notifications
Wait until you have root back
Go into Triangle Away and untick system modified workaround
Proceed with update install (I think you click the notification once the download is complete).
Basically I'm guessing you have to be in the unrooted grace period to start the download, and then it won't check again, so just wait it out so you can disable it, but that's just a guess based on my fumbling around so far. If someone knows better, please correct me.
Cederic said:
Yeah that's the problem I had when I got the first update. What I did the second time was...
Tick system modified workaround
Reboot
Start download of update while root is not available
Click hide or whatever it is, the download will move to notifications
Wait until you have root back
Go into Triangle Away and untick system modified workaround
Proceed with update install (I think you click the notification once the download is complete).
Basically I'm guessing you have to be in the unrooted grace period to start the download, and then it won't check again, so just wait it out so you can disable it, but that's just a guess based on my fumbling around so far. If someone knows better, please correct me.
Click to expand...
Click to collapse
thank you fo such a fine list but still i only get a "couldnt resume with update, try kies or contact samsung".. my status is official according to triangle away.. hmmm
Edit: it worked with kies though, just took painstakinly much time...
Cederic said:
Yeah that's the problem I had when I got the first update. What I did the second time was...
Tick system modified workaround
Reboot
Start download of update while root is not available
Click hide or whatever it is, the download will move to notifications
Wait until you have root back
Go into Triangle Away and untick system modified workaround
Proceed with update install (I think you click the notification once the download is complete).
Basically I'm guessing you have to be in the unrooted grace period to start the download, and then it won't check again, so just wait it out so you can disable it, but that's just a guess based on my fumbling around so far. If someone knows better, please correct me.
Click to expand...
Click to collapse
system modified workaround is disabled in my phone, i have samsung grand i9082 with Super SU pro 1.65 and triangle away 3.00, what to do now to enable it
trychandan said:
system modified workaround is disabled in my phone, i have samsung grand i9082 with Super SU pro 1.65 and triangle away 3.00, what to do now to enable it
Click to expand...
Click to collapse
This forum is for the Galaxy S4 Active, you need to go to the Samsung Galaxy Grand forum:
http://forum.xda-developers.com/forumdisplay.php?f=2288

Delete "Custom: Padlock while phone reboots?

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

[Q] Triangle Away Question

Hi. I have a MJ5 Note 3 rooted via Kingo, and it is completely stock other than that. The KNOX counters are still 0x0 and the Binary is still Samsung Official. However the system status shows Custom and I get the Custom padlock icon during boot. I have seen some references to Triangle Away being able to fix this on the Verizon variant. Has anyone tried Triangle Away on our N900A to remove the custom status? I'm a little hesitant to try it, because I don't want to chance it making one of the settings worse instead of better. I would like to hear if anyone has tried it on this phone and what the result was.
Thanks
Haven't used that. But Wanam exposed will remove the custom logo
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I think it'll work, but why not just use Wanam?
It'll let you do a bunch of other things you want to do too (I don't know what you want to do, but I still feel pretty confident in saying that. The list of tweaks it enables is impressive), so you're going to end up installing it anyway.
DrAzzy said:
I think it'll work, but why not just use Wanam?
It'll let you do a bunch of other things you want to do too (I don't know what you want to do, but I still feel pretty confident in saying that. The list of tweaks it enables is impressive), so you're going to end up installing it anyway.
Click to expand...
Click to collapse
To be honest, it is because I am familiar with Triangle Away and it's a simple app install. As for Wanam, I don't know anything about it or how to install it. It sounds like you first need to have the Xposed framework installed which I don't, and have never done either. I see a lot of people referencing Wanam and how useful it is, but I haven't run across a thread here in the AT&T Note 3 group that, explains where to get it and how to install it on the N900A.
Does it work with all firmware versions, is it easily reversible and the same goes for the Xposed framework?
It's an app on the play store. Just follow the instructions when u download it and it will install the framework. You need to be rooted first.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Xposed framework comes from here: http://forum.xda-developers.com/showthread.php?t=1574401 (I wasn't able to find it in the Play store)
It's one of those things where the app you download installs/uninstalls/manages the framework- it can be reversed by uninstalling through app, and then uninstalling the app.
It is compatible with almost any rooted android 4.0 or higher device.
Wanam comes from the app store, and supports touchwiz roms running android 4.2 or higher.
Those will both work with any version of the note 3 firmware.
I've never used triangle away; I don't understand the motivation for hiding the padlock. I got rid of it with Wanam, but that's certainly not what I got Wanam for.
I just downloaded Wanam and one of the options was to install the framework
Sent from my SAMSUNG-SM-N900A using xda app-developers app
DrAzzy said:
Xposed framework comes from here: http://forum.xda-developers.com/showthread.php?t=1574401 (I wasn't able to find it in the Play store)
It's one of those things where the app you download installs/uninstalls/manages the framework- it can be reversed by uninstalling through app, and then uninstalling the app.
It is compatible with almost any rooted android 4.0 or higher device.
Wanam comes from the app store, and supports touchwiz roms running android 4.2 or higher.
Those will both work with any version of the note 3 firmware.
I've never used triangle away; I don't understand the motivation for hiding the padlock. I got rid of it with Wanam, but that's certainly not what I got Wanam for.
Click to expand...
Click to collapse
Actually what I am trying to do is change the custom system status back to Normal. That is what Triangle Away is capible of doing on some devices that are not running a custom recovery, custom Rom or custom kernel. If all Wanam does is hide the Custom padlock at boot, but the Device status still shows as Custom in the settings, and system still shows Custom in Download mode, then I agree, its not a good use of the tool.
wherestheanykey said:
Actually what I am trying to do is change the custom system status back to Normal. That is what Triangle Away is capible of doing on some devices that are not running a custom recovery, custom Rom or custom kernel. If all Wanam does is hide the Custom padlock at boot, but the Device status still shows as Custom in the settings, and system still shows Custom in Download mode, then I agree, its not a good use of the tool.
Click to expand...
Click to collapse
Just checked, Wanam makes it look normal in device status and download mode, it doesn't just remove the padlock.
I still don't understand why we care if it shows custom in device status and download mode. Does this cause problems with some other software?
DrAzzy said:
Just checked, Wanam makes it look normal in device status and download mode, it doesn't just remove the padlock.
I still don't understand why we care if it shows custom in device status and download mode. Does this cause problems with some other software?
Click to expand...
Click to collapse
Thank you for checking. Did you have to download a separate module for doing this, and if so, which one?
My phone is used for work at a large corporation, and they are funny about unauthorized modifications or "hacking".
wherestheanykey said:
Thank you for checking. Did you have to download a separate module for doing this, and if so, which one?
My phone is used for work at a large corporation, and they are funny about unauthorized modifications or "hacking".
Click to expand...
Click to collapse
Only module you need is Wanam (and the xposed framework, of course)
Ah, I see - I'm not sure how well this will work for hiding your root access from your IT department, since anyone who is even vaguely familiar with android hacking need only look at your app list to determine that you're rooted - otherwise why would you have SuperSU, TiBu, and all the rest of those lovely root-required apps installed.
wherestheanykey said:
Hi. I have a MJ5 Note 3 rooted via Kingo, and it is completely stock other than that. The KNOX counters are still 0x0 and the Binary is still Samsung Official. However the system status shows Custom and I get the Custom padlock icon during boot. I have seen some references to Triangle Away being able to fix this on the Verizon variant. Has anyone tried Triangle Away on our N900A to remove the custom status? I'm a little hesitant to try it, because I don't want to chance it making one of the settings worse instead of better. I would like to hear if anyone has tried it on this phone and what the result was.
Thanks
Click to expand...
Click to collapse
Did you root while you had MJ5 and it didn't trip the counters? I'm suspicious of this Kingo app because I've never dealt with it before. My phone luckily has an older version so I was able to use the Root DeLaVega without issue, but my wife's Note 3 has MJ5 and I want to root it.
Also, Wanam is awesome. I used it to get rid of the Custom mark as well as many other things I love about my phone.
Elemino said:
Did you root while you had MJ5 and it didn't trip the counters? I'm suspicious of this Kingo app because I've never dealt with it before. My phone luckily has an older version so I was able to use the Root DeLaVega without issue, but my wife's Note 3 has MJ5 and I want to root it.
Also, Wanam is awesome. I used it to get rid of the Custom mark as well as many other things I love about my phone.
Click to expand...
Click to collapse
Yes I rooted while on MJ5 with Kingo and it didn't trip the KNOX counters or change the Binary status. All it did was change the system status to Custom and invoke the pad lock during boot. I installed Xposed Framework and Wanam this weekend and it repaired them both.
Thanks again to everyone who helped me with this process.
Elemino said:
Did you root while you had MJ5 and it didn't trip the counters? I'm suspicious of this Kingo app because I've never dealt with it before. My phone luckily has an older version so I was able to use the Root DeLaVega without issue, but my wife's Note 3 has MJ5 and I want to root it.
Also, Wanam is awesome. I used it to get rid of the Custom mark as well as many other things I love about my phone.
Click to expand...
Click to collapse
Kingo doesn't trip the counters.
There's also this method of rooting, which uses the trick used by RDLV - it's a bit of a big deal, though, since it's meant to be a way to recover from a bricked/mangled device:
http://forum.xda-developers.com/showthread.php?t=2559715
DrAzzy said:
Kingo doesn't trip the counters.
There's also this method of rooting, which uses the trick used by RDLV - it's a bit of a big deal, though, since it's meant to be a way to recover from a bricked/mangled device:
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
I watched a few YouTube videos while researching it, and I found several saying it tripped their KNOX flags, that's why I was worried. I successfully used it to root my wife's Note 3 last night without issue. So I had no problems. She too is on MJ5.
Sent from my Galaxy Note 3 using Tapatalk

[Q] Custom Device Status

I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Once you rooted you customized the software. That custom padlock logo is a tattle tale telling on you! I believe your using an xposed module to "fake system status" in order to fool certain people. The xposed module is failing when you see this. It's possible an update, or setting was applied to the module making it fail. Or maybe it's losing it's superuser rights. I had the same thing happen to me. I used triangle away and haven't seen it again. It will surely come back on a factory reset I'm sure.
This happened to me as well and I know its not the xposed because I checked it. This has only happened 3 times and has not happen in like 4 days I checked my system and it says everything is official it did say custom the 3 times it happened I did do a factory reset and it still says official my question is has anyone found a way to unroot for warranty porpoises? Su will not unroot towelroot from what im seeing ...but if everything says official would you even need to worry about unrooting lol I mean if u just factory reset and sent it back I shows no sign of root its all official and no knox tripped ..just a thought ..
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Sent from my SM-N900A using XDA Free mobile app
Freezing "sysscope " on my sgs4 removed the custom unlock boot logo /icon like a charm, however it still bounces back and forth between official and custom on device status when looking.
mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Remove "busy box" file in XBIN system folder. Found this solution on a "Galaxy S4" forum. For a some reason a system keeps some leftovers after the full recovery done. Kinda wrong.

SuperUser no binary

I decided to go ahead & root my S6 using the PingPong Root found here.
All went correctly, but when I go to open SuperSU I get the error 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
Any ideas on how to go about installing the binary needed? Thank you!
Muscle Nerd said:
I decided to go ahead & root my S6 using the PingPong Root found here.
All went correctly, but when I go to open SuperSU I get the error 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
Any ideas on how to go about installing the binary needed? Thank you!
Click to expand...
Click to collapse
You are not rooted then. Try again.
12MaNy said:
You are not rooted then. Try again.
Click to expand...
Click to collapse
Uninstalled both SuperSU & PingPong Root. Reinstalled and had got the same error as before.
This method is in beta, could the binary not be uploaded yet?
Muscle Nerd said:
Uninstalled both SuperSU & PingPong Root. Reinstalled and had got the same error as before.
This method is in beta, could the binary not be uploaded yet?
Click to expand...
Click to collapse
What happens when you run get root on pingpong? Sounds like it's not rooting you. Either 1) you did not open supersu before you ran get root on ping pong. Or 2) it failed to get root (either it tells you failed or it reboots automatically due to kernel panic). If your not getting a pop up saying root was successful, reboot now is recommended, then your not rooted.
_Dennis_ said:
What happens when you run get root on pingpong? Sounds like it's not rooting you. Either 1) you did not open supersu before you ran get root on ping pong. Or 2) it failed to get root (either it tells you failed or it reboots automatically due to kernel panic). If your not getting a pop up saying root was successful, reboot now is recommended, then your not rooted.
Click to expand...
Click to collapse
I don't get that pop up. But my device does reboot.
I tried opening SuperSU prior to PingPong, but it only has the original error 'no binary'. After you press okay, it prompts you to installing SuperSU once again? Odd... Once you install the 'new version' and open that, it'll automatically open PingPong. From there I select 'Download data' then 'Get Root!'. Which then tells me to wait with a popup, and that is when my S6 reboots.
Ok. Now leaving supersu and pingpong installed, reopen pingpong, cancel the install of supersu. Place the phone on a flat surface. Try just 'get root' again. Sometimes background processes can flip out when pingpong panics the kernel to elevate it's privlages. It's taken me 4 or 5 tries a few times I've used pingpong (others only 1 time, I've had to Odin my S6 about 30 times so far lol)
_Dennis_ said:
Ok. Now leaving supersu and pingpong installed, reopen pingpong, cancel the install of supersu. Place the phone on a flat surface. Try just 'get root' again. Sometimes background processes can flip out when pingpong panics the kernel to elevate it's privlages. It's taken me 4 or 5 tries a few times I've used pingpong (others only 1 time, I've had to Odin my S6 about 30 times so far lol)
Click to expand...
Click to collapse
Thanks for the prompt response Dennis!
I opened PingPong, canceled the install of SuperSU, then selected 'Get Root!'. Says my device is not supported (Though it is in the thread for PingPong). I select download data, (Says Device updated, please try Get Root again.) then I select get root. Unfortunately it reboots my S6 after about 2-4 seconds. I'll keep trying!
Aye, do the same steps I said, but add the download data before get root. Try to do it after everything settles from boot but before starting anything else.
_Dennis_ said:
Aye, do the same steps I said, but add the download data before get root. Try to do it after everything settles from boot but before starting anything else.
Click to expand...
Click to collapse
Will do! If this doesn't work after a few dozen tries I may just have to wait for a more stable release, eh?
Muscle Nerd said:
Will do! If this doesn't work after a few dozen tries I may just have to wait for a more stable release, eh?
Click to expand...
Click to collapse
That reminds me, what version are you using? Beta 6 or a different one?
_Dennis_ said:
That reminds me, what version are you using? Beta 6 or a different one?
Click to expand...
Click to collapse
Beta 6
Edit* Uninstalled both applications, and installed the 5.1 beta. When I select download data, it says to retry the Get Root as usual. Then I select Get Root, and it says 'Your device data is still not supported'.
Here's the quote from Idler in the thread. With option C. he says to possible do a factory reset? I have all of my contacts & photos backed up via my pc. Should I possible try and do a reset? Or do you think it's a waste of time.
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears.
If these doesn't help after 5 retries, there could be some issue, please collect the information in /proc/last_kmsg and send it to me.
Note: User reporting installing My Knox or enable other Knox feature (like enterprise provision or KNOX active protection) may cause reboot loop. Be cautious!
Click to expand...
Click to collapse
Ok beta 5.1 does not have hot data then. What is your device? Check settings>about device>baseband
Also from the Q&A in pingpong root thread:
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears​
Make sure to try that.
_Dennis_ said:
Ok beta 5.1 does not have hot data then. What is your device? Check settings>about device>baseband
Also from the Q&A in pingpong root thread:
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears​
Make sure to try that.
Click to expand...
Click to collapse
I have the G925AUCU1AOE2. I've tried all of those aside from the reset
Muscle Nerd said:
I have the G925AUCU1AOE2. I've tried all of those aside from the reset
Click to expand...
Click to collapse
Alright. Best bet. Is reboot. Let settle. Set screen timeout to 10 mins. Turn off all apps you have running in the background. Open pingpong. Download data. Turn on airplane mode. Place on desk. Run root. Don't touch until hopefully it says your rooted. Of course you'll need to I stall beta 6 again before you do the above.
If trying that 5 times doesn't work you'll have to head over to the pingpong thread cause I'm fresh out of ideas lol.
_Dennis_ said:
Alright. Best bet. Is reboot. Let settle. Set screen timeout to 10 mins. Turn off all apps you have running in the background. Open pingpong. Download data. Turn on airplane mode. Place on desk. Run root. Don't touch until hopefully it says your rooted. Of course you'll need to I stall beta 6 again before you do the above.
If trying that 5 times doesn't work you'll have to head over to the pingpong thread cause I'm fresh out of ideas lol.
Click to expand...
Click to collapse
Haha, no worries! I will give that a go.
Yay or nay towards a reset? I have a feeling I'll go through the hassle of resetting my phone & I'll have the same error.
Back up with smart switch. Reset but do not download any app but pongpong. That should help with the error, as it's cause by apps in the background running usually. After root restore via smart switch. All your apps come back, just not the app data unfortunately
_Dennis_ said:
Back up with smart switch. Reset but do not download any app but pongpong. That should help with the error, as it's cause by apps in the background running usually. After root restore via smart switch. All your apps come back, just not the app data unfortunately
Click to expand...
Click to collapse
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Muscle Nerd said:
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Click to expand...
Click to collapse
Glad to hear, now you just have to restore all your apps and stuff. I'd suggest titanium backup, back everything up and transfer to your computer. That way if you ever have to Odin you have all your apps set up and such for when you reroot after. Store them off the phone as Odin will wipe your phone completely usually.
_Dennis_ said:
Glad to hear, now you just have to restore all your apps and stuff. I'd suggest titanium backup, back everything up and transfer to your computer. That way if you ever have to Odin you have all your apps set up and such for when you reroot after. Store them off the phone as Odin will wipe your phone completely usually.
Click to expand...
Click to collapse
Will do, thank you!
Tom Dsgn said:
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Click to expand...
Click to collapse
How do i root my s6 been trying for weeks

Categories

Resources