The file that the LG tool downloads is in a .bin format. Theoretically that should be possible but I'm not sure that anybody has figured out how to convert that to a flashable zip.
[How-to] Guide to Rooting with software version LS670ZVC
- Thread starter drewwalton19216801
- Start date
- Status
Please tell me someone is working on a way to root the Sprint OTA update of LS670ZVC. I just got this phone as a insurance replacement (NOT EVEN CLOSE) for my Samsung Moment, and it was already installed by the damn tech at the store when I picked it up.
I would revert but apparently I can't do that either. Someone HELP.
I would revert but apparently I can't do that either. Someone HELP.
update.zip and the .bin files in LG Update Tool don't work the same way. The former is more like a patch tool. The latter is more like a flash tool.
I would try rooting using the method in the first post anyway. You don't know what procedure the tech used to install VC so there is a chance you can still root. We don't have much experience with units directly from Sprint having VC on them. Most of us are assuming it would be the equivalent of the OTA VC update, but we don't have first hand knowledge.
Thats why I asked that mine be shipped to my house. It should be here any time, I am pacing the door, back and forth, LOL. I dont want that dang update!
Yup, anybody who used the OVA update will be stuck here as well. I'm trying to find a way to trick the LG update tool into thinking my phone isn't up to date so it will run the update but that isn't going so well.
Grrr...I can get the update tool to start the updating process but after checking the phone # it sees the phone is up to date and stops. I want it to install anyway!!!
Last edited:
Has anybody looked at or tried with this tool? I think it is KDZ tool but in a command prompt form.
How-To: Flash Stock LG Rom - Android Forums
How-To: Flash Stock LG Rom - Android Forums
i tried that after bricking. since we get no usb seen on the computer for the device, we're stuck.
however i have not tried for downgrading. will be trying over the weekend if i get my phone back at vc. find out around 3.
If the phone # is what it is going by, you could always change your phone #, run the tool, and change it back. I'm thinking it also checks version information, and possibly all you see as the status breezes by is checking phone #, but who knows.
Huh? At what point are you not seeing your device as a USB device?
It usually only goes away after you run the rage exploit, but before running that, it should show up. Unless you are saying in your bricked phone it wasn't showing up as USB device ?
Phone was bricked then tool was tried to restore it. I know because I did/tried the same with my brick, lol.
My guess is it checks the build prop, cant edit it without root...
So how would I change my phone number in order to try it?
Usually the tool checks the software version and everything right off the bat and if it is up to date it won't even let you click "start updating". So I got around that and the updating process starts but dies at the phone # saying its up to date.
Usually the tool checks the software version and everything right off the bat and if it is up to date it won't even let you click "start updating". So I got around that and the updating process starts but dies at the phone # saying its up to date.
I doubt it is looking at build.prop. The stuff it is reading is at the phone provisioning level. It isn't even getting into the level of linux and filesystems. That particular tool is a flashing tool. It works with lots of LG phones, even ones that aren't android based. I'm not saying it couldn't read build.prop, this is software, it can do anything the programmer wants, just saying it is highly unlikely that is what it is looking given the level of software it is. The LG Update tool is quite different from update.zip. The former is more of a generic flashing tool. The latter is more of a patch method specific to android. That is why your .bin from LG Update Tool is 364MB and your update.zip is only 17MB.
You enter ##MSL# and choose "Edit", change the MDN. When you are done, the phone will reboot. You can make calls but incoming calls won't work. People used to enter the wrong phone # during provisioning all the time, but less often now with HFA.
I understand if your phone was bricked then it might not show up as a USB device, but what I'm saying is for someone who isn't bricked, but just took the VC update OTA by mistake, it could still be worth it to try and use the method in that earlier link to force flash, because they wouldn't have the USB problem.
i think it's been tried (force flashing after ota) but unsuccessfully. there was a few posts regarding this somewhere. they found that the process went further with the lgupdate tool running in the background but still failed to flash anything.
i can't imagine your phone number has anything to do with the update. LG isn't checking with sprints phone number db to see if an update has been push/installed, atleast not to my knowledge and i can't really imagine that.
if it's not the build.prop, then it has to be something else in there that the software checks to see if an update has been applied yet.
i can't imagine your phone number has anything to do with the update. LG isn't checking with sprints phone number db to see if an update has been push/installed, atleast not to my knowledge and i can't really imagine that.
if it's not the build.prop, then it has to be something else in there that the software checks to see if an update has been applied yet.
I would give it a shot but it appears the ROM provided in that post is for the Verizon phone. Could probably just use the .cab file from the KDZ thread and not change the file extension and see if that works.
- Status
Similar threads
Trending Posts
-
[APP][FREE] GoneMAD Music Player - Feature Rich and Highly Customizable Music Player
- Started by gonemadsoftware
- Replies: 0
-
-
-
-
Question Authentication error while connecting to your email provider- Started by Barbarian-CBX
- Replies: 3
Facebook
Twitter
Instagram