• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Did OTA prevent rooted tethering?

C

chrisrach3

Newbie
I was tethering just fine on my stock rooted Rezound up until I did a factory data reset last week. Before the reset, I don't remember whether I had installed the OTA (I assume I had), but it was working fine. So I did a reset because the phone was lagging a bit and I heard it's good to do that every so often, and that it wouldn't affect my root status.

Well, I'm wondering if it did. Here's what happens:

I have it set to Galaxy S III CDMA/LTE (I've also tried the Rezound setting), SSID changed, password set, router fix on...it says:

"Tethering started with errors! Please check 'Show log'."

Then when I turn it off, it says "Unable to start tethering. Is your device 'rooted'?"

Then it says "Your phone is currently in an unknown state - try to reboot!"

Yes, to my knowledge, it's rooted. I rooted before the factory data reset, and it was my understanding that I should be able to do the factory data reset and not lose root. I tried a battery pull, uninstalling and reinstalling the app, trying it under different settings, and etc. Nothing seems to work. Any ideas?
 
Also, just noticed that when I try to go into SuperSU, it reads, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

WTF?
 
if you took an OTA,it removed the superuser binary in the process.

youll need to re-launch recovery,and reflash the superuser files,just like when you rooted the first time. youll then have root access back :)
 
scotty85 said:
if you took an OTA,it removed the superuser binary in the process.

youll need to re-launch recovery,and reflash the superuser files,just like when you rooted the first time. youll then have root access back :)
Click to expand...

Thanks, Scotty. I noticed that one of your threads says that if you take an OTA it will break root. I did take the OTA, but I noticed when trying out the Verizon Redbox app, it noticed that I was rooted. I assume I'm somewhere in between...just want to make sure. :)
 
Well, Scotty, I've managed to screw this up. I found this page: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html

And here's what came up when I tried to flash a recovery:

c:\mini-adb_vigor>adb devices
List of devices attached

...except there were no devices attached. Am I way off?

I thought maybe I was :) so I tried to just boot from recovery (I think). I did the battery pull, volume down + power button, recovery (btw it says "tampered" at the top...should it?), red triangle came up, volume up + power again, then something yellow popped up at the bottom that read "E: Can't open /cache/recovery/command"...
 
tampered is par for the course,nothing alarming. it will disapear if you ever need to run an ruu and get back to stock.

triangle and ! are stock recovery

for no devices in response to adb devices inquiry,make sure usb debug is enabled,and that you ahve drivers installed.

heres some basic info on troubleshooting adb/fastboot connection:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot,enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...

once you get a response from adb devices in the booted OS,and from fastboot devices in fastboot,then the dirctions to launch a temporary recovery will work :)
 
So I haven't messed with re-rooting and was trying to use the Verizon Wi-Fi temporarily until I get the thing re-rooted. But it's gone...any ideas?
 
You must log in or register to reply here.
Back
Top Bottom