• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile/Sprint] Unbrick VM/Sprint F3

Thanks for the replies. The phone is out of warranty. My wife got it when the F3 first hit the market.

So LG is probably not going to help. We'll stall a bit to see if anyone else here can offer a solution, but it looks like she's going to have to buy a new phone.
I'm trying to process the information from your different posts. Pardon me if I ask what you might have answered already.

What version of lg flash tool did you use and did you try the Sprint dll?
 
I'm trying to process the information from your different posts. Pardon me if I ask what you might have answered already.

What version of lg flash tool did you use and did you try the Sprint dll?

I've tried Versions 1.5.1 and 1.8.1 of LGFlashTool.

I haven't tried the Sprint dll. Where can I find it?

However, the dll I used worked before on the same phone.
 
I've tried Versions 1.5.1 and 1.8.1 of LGFlashTool.

I haven't tried the Sprint dll. Where can I find it?

However, the dll I used worked before on the same phone.

Wait, wait...you've flashed successfully to this phone before? You left out that important information, Richard. :rolleyes: That would mean that the errors are being cause from problems on the phone side not the PC software since it has worked before. What modifications has your wife done to the phone since rooting? What instabilities were experience before it soft bricked? Sorry for the 20 questions but to really try and help I need to know all the facts. ;)
 
Wait, wait...you've flashed successfully to this phone before? You left out that important information, Richard. :rolleyes: That would mean that the errors are being cause from problems on the phone side not the PC software since it has worked before. What modifications has your wife done to the phone since rooting? What instabilities were experience before it soft bricked? Sorry for the 20 questions but to really try and help I need to know all the facts. ;)

Ok, sorry for the missing information.

The phone was originally rooted with motochopper. My wife soft-bricked the phone several months ago, when she mistakenly installed the V6 upgrade, before I could warn her not to.

I unbricked it using LGFlashTool, and flashed the V6 stock firmware. Then I re-rooted it using saferoot. It worked fine for a couple of months after that. My wife installed various apps since then, and I moved them to the SD card using Link2SD.

I upgraded to the V7 firmware, using the recommended procedure, re-rooted, and the phone was still working fine.

http://androidforums.com/virgin-mob...4-vm-ls720v7-updating-rooting-unbricking.html

(I have the same phone, and it's gone through the same upgrades and re-rooting without any problems. However, I never soft-bricked it.)

Neither of us did anything unusual to the phone, AFAIK, other than what I've described. But earlier this week, it began to hang -- and the hangs became more and more frequent. Finally, she tried to reboot it, and it hung at the "LG" splash screen, and would not reboot.

As I mentioned, I was able to get it to boot into CWMT, and I tried various things there: Restoring from a CWMT backup, clearing data, reformatting the /system and /data partitions. Always, I got an error message about not being able to mount /system. It's possible that I made the problem worse here.

I thought that, as a last resort, I'd be able to reflash the stock image using the LGFlashTool. But, of course, that's not working either.

I think that's pretty much the whole story.... Any ideas on how to recover the phone would be much appreciated!
 
I couldn't have ask for better info, thanks. Okay with that said, more questions. So how are your Windows command prompt and adb skills? Have you tried installing xclusive36's v7 stock rom with adb sideload in recovery?
 
I couldn't have ask for better info, thanks. Okay with that said, more questions. So how are your Windows command prompt and adb skills? Have you tried installing xclusive36's v7 stock rom with adb sideload in recovery?


I can find my way around with the command prompt. (I'm retired, after a 32-year career in IT. For a lot of that time, command-line -- in various operating systems -- was all there was!) And I've used adb once or twice -- but not the sideload feature.

So, with some clear instructions, I'd love to try adb sideload.

Can you point me to how to do it? Much appreciated!
 
This should be a breeze for you. First you'll need to download the stock zv7 rom. Once you have it place it in the same folder as adb.exe and open your command prompt there as well. We'll move to the phone now, you'll come back to the prompt window in a minute. Now if you haven't already done so, enter recovery and plug in your usb cable into the phone. In recovery go to [install zip] under the sub-menu select [install zip from sideload]. Recovery is now ready to receive the zip file. Okay, go back to the command prompt window and type:

adb sideload Odexed_Stock-LS720V7.zip

Hit enter and that's it. You should see the transfer percentage in the window. It's a large file so it may take some time. If for some reason you get a transfer error wait a second or two and run the command line again. I can't say for sure that this is going to solve the problem but you gotta try everything at least once...right. Good luck. :D
 
This should be a breeze for you. First you'll need to download the stock zv7 rom. Once you have it place it in the same folder as adb.exe and open your command prompt there as well. We'll move to the phone now, you'll come back to the prompt window in a minute. Now if you haven't already done so, enter recovery and plug in your usb cable into the phone. In recovery go to [install zip] under the sub-menu select [install zip from sideload]. Recovery is now ready to receive the zip file. Okay, go back to the command prompt window and type:

adb sideload Odexed_Stock-LS720V7.zip

Hit enter and that's it. You should see the transfer percentage in the window. It's a large file so it may take some time. If for some reason you get a transfer error wait a second or two and run the command line again. I can't say for sure that this is going to solve the problem but you gotta try everything at least once...right. Good luck. :D

Thanks! Tried it, but at 50% I got

* failed to write data 'protocol fault <no status>' *

So no luck.

Edit: Tried several different zip files, versions V6 and V7, all with the same result. Failed at 50%.
 
Thanks! Tried it, but at 50% I got

* failed to write data 'protocol fault <no status>' *

So no luck.

Edit: Tried several different zip files, versions V6 and V7, all with the same result. Failed at 50%.

Hmmmm...I'm trying to think of something else but I gotta tell you, I think it's fubar. The phone not letting you install system or data partitions is a major problem with no solution that I know of the way thing stand. The only thing I can think of at all is that your GPT (Grande Partition Table) became corrupt, some how. There are 30 partitions on the f3. Data, System and Cache being three of them. To fix them you would use the Flash Tool but that doesn't work in this situation. I'm at a lose at the moment on what to do next. :(
 
Hmmmm...I'm trying to think of something else but I gotta tell you, I think it's fubar. The phone not letting you install system or data partitions is a major problem with no solution that I know of the way thing stand. The only thing I can think of at all is that your GPT (Grande Partition Table) became corrupt, some how. There are 30 partitions on the f3. Data, System and Cache being three of them. To fix them you would use the Flash Tool but that doesn't work in this situation. I'm at a lose at the moment on what to do next. :(

Well, it was worth a try.

From some of the other postings here, I'm not the only one to have experienced this. And no one seems to have found a solution.

Thanks again for all the advice! Even though we didn't succeed in the end, I really appreciate it!
 
Well, it was worth a try.

From some of the other postings here, I'm not the only one to have experienced this. And no one seems to have found a solution.

Thanks again for all the advice! Even though we didn't succeed in the end, I really appreciate it!

Your welcome, I just wish I could have come up with a solution for you. :(
 
Has anyone had the issue of the LG Flash Tool starting the Flash, but sticking at 3%? It says "...PrimaryGPT" as its last message, and then just sits there. At over 700 secs, I've restarted the flash, and used both the VM720 and the LS720 dll files.

Is there a difference between a BIN file and a TOT file?
 
Folks, I've been through this forum string over and over... everything seems good, BUT fails on download.

I can't post my result image since I'm too new, but essentially:

I press the yellow arrow
I disconnect the USB
LG Flash Tool says ok after a few seconds
I plug the phone in
It begins the download.
-Here's what shows up in, line by line, in the LG Flash Tool window for COM41:
PID: NULL
IMEI: 990002530123171

990002530123171
LGLS720
LS720ZV6_03
LS720ZV6_03
Model : LS720
Initializing
USB Connection Established
Flashing
...PrimaryGPT
...PrimaryGPT
...PrimaryGPT
...PrimaryGPT
...PrimaryGPT
:: Error ::
F0000002

Then the window title for COM41 says "Download FAIL!! (37 secs)

Now what? Thoughts? I've tried two different DLLs, different LG Flash Tool versions (example above was LG FlashTool V1.8.1023).
 
Folks, I've been through this forum string over and over... everything seems good, BUT fails on download.

I can't post my result image since I'm too new, but essentially:

I press the yellow arrow
I disconnect the USB
LG Flash Tool says ok after a few seconds
I plug the phone in
It begins the download.
-Here's what shows up in, line by line, in the LG Flash Tool window for COM41:
PID: NULL
IMEI: 990002530123171

990002530123171
LGLS720
LS720ZV6_03
LS720ZV6_03
Model : LS720
Initializing
USB Connection Established
Flashing
...PrimaryGPT
...PrimaryGPT
...PrimaryGPT
...PrimaryGPT
...PrimaryGPT
:: Error ::
F0000002

Then the window title for COM41 says "Download FAIL!! (37 secs)

Now what? Thoughts? I've tried two different DLLs, different LG Flash Tool versions (example above was LG FlashTool V1.8.1023).

That exactly what happened to me. Unfortunately, I was never able to find a solution, and my wife had to get a new phone.
 
No, unfortunately, it goes to only 3%, then reports "Download FAIL!!". So the reflash hasn't completed, and the phone won't reboot.

I have a VM optimus F3 that started acting badly after an OTA system update. I read this thread about 5 times and decided to try to restore to the V5 (assuming that was the out of box version). Read all the directions and comments. Here's my experience.

I reflashed the phone per the instructions, it worked.

Then the system update was asking to upgrade, and I kept dismissing it.

Then the phone acted a bit laggy so I decided to let the system update.

Then the phone froze, no response. Any battery pull and restart ended on the VM splash screen.

So I reflashed to V5, it worked.

Then I wanted to see if the V6 and/or V7 from the forum sources would work. I tried to flash to V6 and I got the failure quoted above with the 3% and 30 or 37 seconds.

All of this was with the 151 version of the flash program.

I tried the 181 version and had the same failures.

I tried these repeatedly. (V5, V6, V7 multiple times)

The last time (today) I tried to flash with the 181 program with the VM DLL and V5 ROM I got the same 3%/37 sec failure. I left the computer sitting there at the 3% fail point and went out to get some pizza (over an hour). When I came back I heard the phone talking to me about the hands free activation. It was working.

So I would say to all those who have hit that 3% error point, take a break watch a TV show, it's possible the phone will finish the process.

The time frame for this was over the last few weeks.

I will be playing with the phone over the next few days to see if it still hangs in there and will report any findings.

This was my wife's phone. I bought her an LG Volt, took the F3 off the Virgin system. I will be trying it on wifi to see how it performs.
 
Any ideas as to what might have cause the error?

I'm thinking the internal memory has bad sectors. I must of hit 1 or more of those running the unbrick tool.

When It wouldn't flash correctly, I rebooted the phone and it fully booted up. It was giving me the same issues I had before I ran the tool. The tool just didn't get far enough to change anything.

I put it back into download mode and tried it a few more times before it finally worked. I've used the tool on that phone a few times before and it always worked like it should. I hope I don't run into it again. I thought I lost it.
 
I'm thinking the internal memory has bad sectors. I must of hit 1 or more of those running the unbrick tool.

When It wouldn't flash correctly, I rebooted the phone and it fully booted up. It was giving me the same issues I had before I ran the tool. The tool just didn't get far enough to change anything.

I put it back into download mode and tried it a few more times before it finally worked. I've used the tool on that phone a few times before and it always worked like it should. I hope I don't run into it again. I thought I lost it.

Well at least you got it to work. :congrats:

This phone is so frustrating...
 
Ok so, let me know if this sounds right due to my little understanding of this all.. The flash tool recognizes my Boost Mobile phone, the only problem I am having is I cannot find the driver information in device manage to change..
So I'm just wondering if all I have to do is find and correctly install the correct driver to work or what?
Or if anyone knows a different way I can un soft-brick this phone.. I can put in download mode or it gets stuck on black screen while the start-up buttons glow different colors.
I don't care if I have to fully reset it or whatever I just want to re-root and figure out how to upgrade it again for the fun of it. this cannot be that hard I'm just new to all this nonsense
 
Ok so, let me know if this sounds right due to my little understanding of this all.. The flash tool recognizes my Boost Mobile phone, the only problem I am having is I cannot find the driver information in device manage to change..
So I'm just wondering if all I have to do is find and correctly install the correct driver to work or what?
Or if anyone knows a different way I can un soft-brick this phone.. I can put in download mode or it gets stuck on black screen while the start-up buttons glow different colors.
I don't care if I have to fully reset it or whatever I just want to re-root and figure out how to upgrade it again for the fun of it. this cannot be that hard I'm just new to all this nonsense

Believe this works for Boost phones. Read OP and all fine print. Believe there are two Dll files you can try.

Post back if issues.
 
ok, so i unrooted my phone a couple months ago using your intructions. worked great. but today i went to do it again, and it's not working. it keeps getting stuck on flashing "primary gtp". it's driving me crazy cause it worked fine last time. please help i have no phone till then.
 
Well I couldn't get past the "PRIMARY GPT" error. But luckily Radioshack's "It happens" service plan covered it. I just played dumb and said "idk what's wrong with it. Every time it restarts it does a system restore. Maybe it.s got malware?" Lol. "I think it needs to be flashed, whatever that means"
Radioshack guy-"yea idk what that is." lol just grabbed me a new phone off the shelf. Man am I glad I paid that one-time fee of $20 when I bought the phone. Although if u wanted to insure the replacement, it would have been $60
 
I read the post...twice! Do you have an "Unbrick" for Verizon Samsung GS3?
Thanks Bro

:) Wow, I feel amazingly Lucky, W00T! Yesterday, I was hopelessly frantic, trying to get this @*?/#X phone to work, having invested a lot of $$$ into my daring "root" venture.

I had rooted the VZ Galaxy S3 using "towel root", verified by Root Checker, and being excited & giddy as a school-boy, invested in SuperUser Pro, titanium backup premium, and also loaded DU Boost & Juice Defender!

:D Thinking this "stuff (root tools)" is so well designed...it is virtually idiot proofed. Emboldened by my successes, I loaded CWM ROM Mgr....upgraded to CWMt. :smokingsomb: This all seemed too easy, but nooby as I am, I went further into the abyss. CWM had ROMs to upload, and dammit ROMs I shall have...after all why root the phone if not to have ROMs (not even being entirely sure what a ROM was).

:o I found JRUMMY - Dancing Droid, and I figured something simple like that would be a Great Start. :confused: I selected what I wanted...loaded it easy enough...and then CWM asked if I wanted to install into recovery or something?!?? Hmmm, why not, the App knows what "I'm" doing.

:mad: The phone shut down, and starts a reboot, but suddenly a big "yellow triangle" with an exclamation mark inside of it pops-up, and a message saying "Verizon Wireless found an unauthorized System App on the phone (paraphrased)", and to turn the phone off & take it into a VZ wireless store! Ahhh, WTF!!!! :vollkommenauf:

:idea: I know, I'll do a reset by pulling the battery...SD...SIM...nothing. I go to CWM to contact the Dev...still waiting! The illustrious "titanium backup pro"...auto-response...still nothing! Crackers, now what do I do? So, I went google, and WOW...what a bunch of rocket scientists more than willing to help...ha!

:( In despair, I figured I'd have to wait for one of the "root Devs" to respond, and without a phone or text. I went to shutdown my PC, and on the new Windows 8.1 desktop was a VZ diagnostics App for my Samsung GS3! I plugged in the phone, ran the App, and BLAMO! My phone restarted to pre-brick condition, root and All!

:cool: Not bad, for a noob who should have gone back to "stock"!
 
Back
Top Bottom