Open GoogleCodeExporter opened 9 years ago
What were the steps you took to get to the rooted GB you're at right now?
I used to have the exact same problem, then the ApeX ROM pretty much crashed my
DroidX, so I RSD'd back to the last working Froyo (2.2.340). I didn't restore
any of my app data or Nandroid backups, just rooted Froyo and applied the GB
updates as well as reinstalling the DX tether patch with each step (each step
being at Froyo 2.2.340, GingerBread build-4.5.157, GB build-4.5.588, and GB
4.5.595). Then after getting to the latest version of GB, I installed a custom
ROM, the tether patch again, and lastly, the latest version of WiFi Tether, and
it started perfectly. I was also pretty stoked it wasn't ad-hoc wireless
either, but an actual wireless network.
While I was on ApeX (and other gingerbread ROMs before it), I could never get
wifi tether working and every time I tried, my phone's browser wouldn't work
and Verizon thought any regular data use was tethered data. I tried every
version of Wifi Tether, nothing worked. I chalked it up to Verizon cracking
down and gave up. But since my phone was screwed and I had to start all over, I
decided not to take any shortcuts, made sure the tether patch was applied with
each update, and restored all my previous apps but none of the previous app
data.
Obviously, completely wiping your phone and starting from scratch is a hassle
if you just want wifi tether, but if you really need it, get Titanium Backup
AND MyBackup Pro (between the two, you can back up apps, call logs, text
messages... pretty much everything so your phone will still be the same) and
then once you upgrade your phone back to where it is now, you can restore all
your apps just not the app data, then download the latest Wifi Tether and
you'll be good to go.
Original comment by matt.kel...@gmail.com
on 29 Jul 2011 at 8:32
There's a nasty hack that will get Wifi Tether working again:
http://android.stackexchange.com/q/13223/2300#13436
Original comment by josh3...@gmail.com
on 26 Sep 2011 at 10:46
Original issue reported on code.google.com by
boonel...@gmail.com
on 3 Jun 2011 at 3:26