I think I am overwhelmed with info... Want to revert and allow OTA

stygshore

Member
Dec 2, 2010
14
0
0
LG Optimus S
Build Number: ThundeROM v1.6.2
Kernel: 2.6.32.26 Thunder beezy@beezy #1
SW Version: LS670ZV9
Phone is Rooted - did it manually initially and then used Z4Root the second time I did it.

I have read through a ton of the how to instructions, and I am honestly confused on which one I need.
Can someone direct me to the easiest set of instructions to allow the latest Sprint OTA? There isn't anything on my phone I HAVE to keep, so if it requires a total dump, that's fine.

Work is paying for my phone now, so I need to go legit :)

Styg
 
is there a trick to doing ADB from the term emulator? I can not get it to work via the USB on this laptop for some reason.

don't suppose any of you experts are around on AIM that could give me a hand?

Styg
 
is there a trick to doing ADB from the term emulator? I can not get it to work via the USB on this laptop for some reason.

don't suppose any of you experts are around on AIM that could give me a hand?

Styg
im on gtalk... and u need to install the LG Mobile Update tool. From there u need to install the drivers for your cell. THEN you can use ADB
 
Just curious... why do you need to use the stock ROM and everything just because your work is paying for your phone? It's not like you lost any features using a custom ROM.
 
Technically I don't, but if I am going through the process to unroot and revert back to get the latest OTA patch to fix that android security issue, I might as well just add the hotspot to my phone plan since its not coming out of my pocket any longer. I really only rooted to have Wifi, I cant think of anything else I really needed it for

Styg
 
installed ADB and the sdk and update tool... now I think I am worse off, I stll cant do ADB from the command line, and now although my phone shows ADB in the status bar it says adb not found when I try and do the push from terminal emulator...

Styg
 
installed ADB and the sdk and update tool... now I think I am worse off, I stll cant do ADB from the command line, and now although my phone shows ADB in the status bar it says adb not found when I try and do the push from terminal emulator...

Styg
make sure you have ADB Interface showing in your Device Manager...

Then you need to pull up command prompt.. cd to the folder you have your adb in....

and then type.. adb devices

That command should show you ANY devices connected that are seen via ADB.
 
installed ADB and the sdk and update tool... now I think I am worse off, I stll cant do ADB from the command line, and now although my phone shows ADB in the status bar it says adb not found when I try and do the push from terminal emulator...

Styg

To me it sounds like your command paths are not set up properly.