Hey everyone, first post here
First of all, thanks to everyone that collaborate with this awesome guide, great work!
I'm having a little issue and being the noob I am, I'm scare to make any move so I thought about asking for a little help...
I followed the guide here and was able to root my AT&T captive 2.3.5 without any issues. Everything was working fine... for a while.
After rooting, superuser was working fine. As the guide recommended I updated the SU app from the store, and also installed busybox using the smart install thingy it has (didn't mess with the settings it recommended). Lastly, I updated the SU binary to 3.1.1 through the app as it started asking for that.
I believe that either after installing BB or updating the SU binary, something went terribly wrong. What happens now is that any app that requests root permissions either fails to get the SU prompt up or hangs the phone completely. Busybox reports that it couldn't open a shell with root, rootchecker just hang checking and never ends, link2sd and a couple other apps I tried just hang everything completely requiring a battery pull. The superuser app itself hangs if trying to update the su binary again or any other root operation...
Is it possible that either the BB install or SU binary update messed with my root? I was thinking about applying the root process again, but I'm afraid that it might cause issues or even brick the thing, being in its current unstable status... in theory it should just overwrite with the version of su that's inside the patch and be happy, but that's just my theory
Anyone experienced this before? Any insights? I was also thinking about applying a CM ROM, in which case it might be better to directly apply corn kernel to also get CWM for recovery mode? Would that be safe to apply on top of this?
Thanks a lot in advance!