- 03-27-2011, 12:30 PM #176
There is no version V9VC or V9VD, only V8, V9, VC, VD. You are at V9 right now. It is rootable and your hotspot will work.
You can go to VC if you'd like and personal hotspot will still work, but rooting could get messed up unless you follow specific sequences. VD the personal hotspot will work if you install a custom ROM, TR1.8.2
If all you want is personal hotspot to work on stock ROM, just stick with what you have now, it is less trouble.
- 03-27-2011, 02:52 PM #178
I just wanted to say how grateful I am to you (and this forum). This thread was a life-saver. As a newbie, I really just wanted to reclaim my wi-fi hotspot, and this did it for me. If I ever feel brave enough, I may try rooting, but for now, I'm ecstatic with this simple fix!
For all who are curious, I have an Optimus S, and had just received the evil VD update. I followed the instructions for flashing to V9 using the kp500. And the entire procedure was painless! I have zero programming experience, and it took me about 30-40 minutes total, beginning at step a.
The instructions were amazingly clear and easy to follow. Here is just one MINOR edit that would help newbies.
For step k), I had a brief moment of confusion when I tried typing "KP500-Utils-EN.exe" into the command prompt, and it didn't work. I had just performed the optional checksum, and it took me a couple minutes to realize that I first needed to enter, "C:\KP500-Utils-EN-v0.4.2>dir" before I could then type "KP500-Utils-EN.exe" to run the executable file.
Like I said, I'm a newbie. I barely I understand what I did. I'm just glad it worked! Thanks again.
Glad you got it working. I was about to modify the instructions to reflect your suggestion but realized that what you did couldn't have affected whether KP500 ran or not. "dir" just gives a directory listing. It doesn't affect where programs are run from or whether programs can run.
I think possibly there was a small typo when you typed KP500-Utils-EN.exe the first time and after you entered "dir" then reentered KP500-Utils-EN.exe, it was entered correctly.
- 03-27-2011, 06:10 PM #180
- 6 Posts
I have two Win7 x64 systems (one Pro, one Enterprise), and both complain that the LG drivers are unsigned and refuse to install the Android Platform Sooner Single ADB Interface (lgandadb.sys). Is this critical? Is there a signed copy of this driver or a workaround? I'm not exactly a Win7 expert...
Found a workaround; rebooting Windows and pressing F8 to disable driver signing enforcement.
Last edited by cowboydren; 03-27-2011 at 06:24 PM.
- 03-27-2011, 10:23 PM #181
- 9 Posts
thought you might want to add to ur orig post located at http://forum.androidcentral.com/lg-o...diag-mode.html
to prevent the phone From Getting ota Updates when downgraded to V9, Go into ##lgservicemenu>Enter SPC/MSL> Phone Self Service> Click>Choose Edit Change settings to 0.0.0.0 (Proxy)> Port 80>and server to somthing like Google.com Or NoOta.org (any thing of your flavor
THEN press The Mag Glass Button or the Menu Button To Set the Change
- 03-28-2011, 02:01 AM #183
- 9 Posts
SORRY IT IS ## DATA!!
i feel like a noob <8-)-k
It could affect the updating of the prl, but i had no problems (after using qpst prl from another phone, x-fer to optimus, then dial *228 on cricket) getting new prl updates
when i was on sprint it also still updated by dialing *228 or *22800 and or (ymmv) *22801 *22802..... - *22809
Sprint does there updates a little different than cricket. PRL is not as big a deal as Update Profile because as you mentioned, you can load it with other tools. Update Profile though is nice to have working because you if you mess up your data logins, that is the worse time to figure out Update Profile doesn't work.
Anyway, I'm not really opposed to adding the info you provided, but if there is an easier solution which doesn't even require MSL, I think that will be best for most people.
- 03-28-2011, 05:35 AM #185
- 4 Posts
I have a few questions
last week I updated my phone and the hotspot widget stopped working so I read around on the forum and found this post and reverted back and everything works great now, but I now keep getting the system update reminder to update to LS670ZVC. Is this the update that killed the hotspot widget? If the LS670ZVC update is what killed the hotspot widget how can I get my phone to stop wanting to update. I am currently on android version 2.2.1 and SW version LS670ZV9. thanks for any help in advance
- 03-29-2011, 05:28 AM #187
- 03-29-2011, 07:12 PM #188
- 04-02-2011, 10:01 PM #190
- 04-03-2011, 12:23 AM #191
- 5 Posts
- UberROM 1.4.1
Just wanted to say that I followed the directions to the "T" and everything worked as prescribed. Thanks a million. Even the Battery pull/More info trick when the nag message pops up worked. My wife was PISSED when VZD loaded. Now she's back at VZ9.
Props to all involed. Now on to root my Samsung Moment.
- 04-03-2011, 12:30 AM #192
Last edited by sfhub; 04-04-2011 at 03:39 AM.
- 04-04-2011, 07:33 AM #195
- 04-04-2011, 06:56 PM #197
- 7 Posts
Ok... this is driving me nuts. Ive been fighting this thing for 3 days now. I have spent the past 3 yearsjailbreaking my iPhone, and never had trouble. This is almost confusing, but in the end, I still cant get a valid result.
I have followed the instructions here to revert back to V9, had to use the bling method of doing everything from there, as I have a new phone withthe new display. I managed to get z4root to report that it had rooted, yet executing an ADB SHELL in cmd promot still returns a $, not a #. So Im guessing it actually isnt rooted. From there in the instructions Im stuck. I cant go on without a proper root.
Ive fought to this point 5 times, and have run out of time and had to revert back agian to VD. What am I missing?
EDIT---- BTW, Im trying to work my way thru this quide...http://forum.androidcentral.com/lg-o...-ls670zvd.html
- 04-04-2011, 07:22 PM #198
- 04-04-2011, 08:56 PM #199
Don't worry, the su prompt thing is job security for folks around here
BTW instead of doing things blindly, you should use Android Screencast. That suggestion is there in the RED warning #2.