Towelroot questions once again.

Okay hi everyone, I literally just joined the forum, and I have questions about towelroot. I tried to use it a few minutes ago on my Samsung Galaxy A3, and it had the message "phone not supported". So I used the method where you input the specific code (the one for Galaxy devices) and when I pressed the "Make it ra1n" button, it went orange, and the app did nothing after that. Nothing more happened, no failed or succeeded message at all. Is there a way to fix this? Even if it is the temporary root, I can work with that, I'd just like to know why it won't respond and if there is a way to fix this particular problem. Thanks in advance.

~Panda

How to root once cm12 is flashed?

Hi guys I rooted my phone and installed the latest cm12. Nightly but now it seems it has removed my root access? Other this is the ROM is running Nice. How can I root my device now that I am on cm. As I cannot see the enable USB debugging in the settings please help thanks

Once I unlock the bootloader wifi wont turn on

I had a custom ROM till sunday because I lost wifi, so I flash another rom same issu, did a restore and got back to factory state and wifi started workign again, I just unlock the booatloader to do a root and again no wifi, any ideas (Nexus Sprint)

Mysterious vibrating once a second

I saw some very strange behavior from my Verizon Galaxy S5 (running OptimalROM) this morning. I was watching a video at my computer with the phone (screen off) sitting on my thigh, when I start hearing something about once a second -- I pause the video, and figure out it is my phone -- I pick up my phone and discover the noise is actually the phone vibrating. It is vibrating for a full second, then nothing for a second, then it vibrates again for a full second, and this kept repeating. I turned the screen on, thinking there was an incoming call or an emergency alert, or something, but there's no phone call and no notifications of any sort. After the vibrating continued for about a minute, I finally decided to reboot the phone to see if that would stop it -- which it did, and it has yet to reoccur.

I've never seen this behavior from any Android phone, so I thought I would ask the community if they've seen it and know why it was doing it.