SW Version LS670ZVD?

Has anyone tried the hotspot widget on VD?
If you do try it could you let us know if it's still working.
 
Is there any reason to hold off on updating to it? I have a bit of extra time this morning...
 
Has anyone tried the hotspot widget on VD?
If you do try it could you let us know if it's still working.

I haven't tried the Hotspot Widget but Wireless Tether for Root Users works just fine. In fact, I am writing this post while tethered with it.

So LG fails miserably once again.
1) They try to make it unrootable. That obviously didn't happen as I was able to root it 30 seconds after updating.
2) They didn't bother to patch the wifi tether exploit so now we get to screw Sprint out of ~$30 a month. Nice going LG.

Is there any reason to hold off on updating to it? I have a bit of extra time this morning...

Not in my opinion, as it seems to run a bit faster and boot a bit faster. It also probably fixes the LG logo hang issue.
 
I haven't tried the Hotspot Widget but Wireless Tether for Root Users works just fine. In fact, I am writing this post while tethered with it.

So LG fails miserably once again.
1) They try to make it unrootable. That obviously didn't happen as I was able to root it 30 seconds after updating.
2) They didn't bother to patch the wifi tether exploit so now we get to screw Sprint out of ~$30 a month. Nice going LG.



Not in my opinion, as it seems to run a bit faster and boot a bit faster. It also probably fixes the LG logo hang issue.

Wierless tether for root users 2.07? That's ad-hoc right? The widget runs in AP mode so you
Can use it with other andoirds or ps3 wii etc...

Thanks for the update.

The widget iam talking is https://market.android.com/details?id=at.mysandbox.android.hotspotwidget&feature=search_result
 
i think they fixed wifi tehter when i try to use it from the widget it disconnects my 3g then waits then says hotspot unavailable so it is trying to use the proper (bad in our case) profile now.
 
i think they fixed wifi tehter when i try to use it from the widget it disconnects my 3g then waits then says hotspot unavailable so it is trying to use the proper (bad in our case) profile now.

They fixed the exploit that the Hotspot Widget takes advantage of, but Wireless Tether for Root Users 2.0.7 works wonders.
 
So if I am understanding correctly, there is no way to run Wireless Tether AP mode under this new version now?
 
I updated using the tool while running LegoROM.
Followed the guide. All went well.
Flashed nROM and my Android version went back to 2.2.1, and my Baseband went back to MVC, but my SW Version is still at ZVD. Did I do something wrong, or is this normal?
Thanks for all your hard work!
 
The trick is to update using the LG tool but YOU HAVE TO HAVE ZEFIE'S XIONIA CLOCKWORK RECOVERY INSTALLED FIRST!!!

I currently have the ThundeRC custom recovery installed, but am one of the few users that have the new LCD hardware, so the screen is blank in recovery mode. Do I need to install the stock VC recovery first before switching to Xionia Clockwork Recovery? I wasn't sure, since part of the procedure is
cat /sdcard/flash_image > /system/bin/flash_image
Since I already concatenated the flash_image for ThundeRC to the stock flash_image, will doing it again break anything if it's not stock?
 
I currently have the ThundeRC custom recovery installed, but am one of the few users that have the new LCD hardware, so the screen is blank in recovery mode. Do I need to install the stock VC recovery first before switching to Xionia Clockwork Recovery? I wasn't sure, since part of the procedure is

Since I already concatenated the flash_image for ThundeRC to the stock flash_image, will doing it again break anything if it's not stock?

This command doesn't flash an image to your phone, It just copies the flash_image utility to your phone so you can flash images in the future.

In order to flash a recovery image, you should have run a command like this :

flash_mage recovery [recovery image to flash]
 
This command doesn't flash an image to your phone, It just copies the flash_image utility to your phone so you can flash images in the future.

I understand this. However, I don't believe it copies the file, it actually concatenates the file to the end of an existing file.

My question was, if I have already done this with the flash_image supplied with ThunderRC, can I do this again with the Xionia Clockwork flash_image, or do I first need to get ahold of the stock flash_image file. When I first installed ThundeRC, I stupidly forgot to backup the stock flash_image file.
 
flash_image is flash_image is flash_image. There is no such thing as a "stock" flash_image. And it only appends to the end of the file if you use >> instead of >.

For example:
cat /sdcard/su > /system/bin/su
The above command essentially replaces /system/bin/su with the contents of /sdcard/su

cat /sdcard/su >> /system/bin/su
The above command appends the contents of /sdcard/su to the end of /system/bin/su

Background in Linux administration FTW.
 
Last edited:
Ok, thanks for that! I guess I won't have a problem then.

I assumed it was doing a concatenate. I figured cp would have been used if it was only for a copy. :-!
 
flash_image is flash_image is flash_image. There is no such thing as a "stock" flash_image. And it only appends to the end of the file if you use >> instead of >.

For example:

Looking to do this when I get home later tonight (updating to VD that is). Just wanted to know if I could get any opinion from you as to the validity of the method I mentioned in this post:

http://forum.androidcentral.com/lg-...s/66736-sw-version-ls670zvd-4.html#post700943

Thanks in advance.
 
Someone please correct me if I am wrong, but I believe wireless tether won't run on ThundeROM 1.7 as wireless tether requires a non stock kernel and TR 1.7 is running a stock kernel.
 
Someone please correct me if I am wrong, but I believe wireless tether won't run on ThundeROM 1.7 as wireless tether requires a non stock kernel and TR 1.7 is running a stock kernel.

That is correct, it requires a netfilter-enabled kernel. I tried it again a little while ago just to make sure because in the app's notes it says that if it force-closes to reinsall. Blew up on me again so I read further down and saw the requirements. TR 1.7 uses stock VC kernel so it won't work.
 
Last edited: