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

Root [Virgin Mobile/Sprint] [Recovery][VM]CWM 6.0.4.8 Touch for the LG Optimus F3

From what I'll learned about the Metro-PCS\T-Mobile side they have been using the 'reboot-recovery'. For some reason using the key combo F-R's the phone. You can try it. If you do and get no reset let me know if you would, please. Oh, when you get a F-R, the /data and /cache wipe doesn't happen until after you leave recovery. So you must go thru boot and then back into recovery to restore or backup. Just the way it works I'm afraid.

How do I reboot-recovery?
 
How do I reboot-recovery?

You can use adb in windows cmd prompt, a terninal on your phone (the command is "reboot recovery") or the Play store has dozens of apps (the easiest method). I use Quickboot for reboot and power-off functions (only) since we can't use the R-R command, but it has it in the menu. Lets hope this works for you! :)
 
You can use adb in windows cmd prompt, a terninal on your phone (the command is "reboot recovery") or the Play store has dozens of apps (the easiest method). I use Quickboot for reboot and power-off functions (only) since we can't use the R-R command, but it has it in the menu. Lets hope this works for you! :)

I tried to reboot to recovery through ROM Toolbox Pro, but I got another factory reset.
 
I tried to reboot to recovery through ROM Toolbox Pro, but I got another factory reset.
Yeah, I kinda thought that's what would happen. In order for the VM to have loki support running on zv6 you have to revert the aboot image. Which is in the installers, btw. So now you have the VM aboot on your T-Mobile device. From what I can tell they are very close. They are different enough to not work with recovery though. So I assume you boot into the system fine...right? It's just recovery you can't use right now.
 
Yeah, I kinda thought that's what would happen. In order for the VM to have loki support running on zv6 you have to revert the aboot image. Which is in the installers, btw. So now you have the VM aboot on your T-Mobile device. From what I can tell they are very close. They are different enough to not work with recovery though. So I assume you boot into the system fine...right? It's just recovery you can't use right now.

Yep, I can boot into the system, but I'm not gonna try the recovery again. haha
 
Yep, I can boot into the system, but I'm not gonna try the recovery again. haha

Ok, so sammyz found the KDZ file for your f3 variant. You'll have to google the method for extracting the files from it (it's like a zip file...kinda, lol). You can get your original aboot image from there or ask around in the posts. I would try the recoveries over on the M-PCS/T-Mobile subforum and see if you have better luck. In the loki patch source code the M-PCS & T-M are listed as one aboot target for both devices. The aboot is the key part to the loki exploit patching the boot or recovery images, btw.
 
Ok, so sammyz found the KDZ file for your f3 variant. You'll have to google the method for extracting the files from it (it's like a zip file...kinda, lol). You can get your original aboot image from there or ask around in the posts. I would try the recoveries over on the M-PCS/T-Mobile subforum and see if you have better luck. In the loki patch source code the M-PCS & T-M are listed as one aboot target for both devices. The aboot is the key part to the loki exploit patching the boot or recovery images, btw.

That's all too confusing for me! :p
 
Well, I tried the cwm from the Metro PCS/T-Mobile thread, and that didn't work either...that particular recovery works with Metro but no T-Mobile. *sigh* Maybe someday we'll get one working for T-Mobile.
 
Well, I tried the cwm from the Metro PCS/T-Mobile thread, and that didn't work either...that particular recovery works with Metro but no T-Mobile. *sigh* Maybe someday we'll get one working for T-Mobile.

Don't give up on me yet. I'm in 'dog with a bone' mode. The reason it didn't work is you still have the vm aboot image on your phone. Give me some time. If you're interested send me a pm and I'll see what I can come up with.
 
Although I almost completed a hard factory reset by holding down Power/+ combo instead of the Power/- combo everything works perfectly. Thanked.

Edit: Thank god it's the 'touch' rec. :)
 
That's the thing though, I used the button combo and it factory reset my phone. I never had that problem on my elite
 
That's the thing though, I used the button combo and it factory reset my phone. I never had that problem on my elite
It sounds like the flash didn't work and you still have the factory recovery installed. Have you tried the Reboot Recovery command to see if that works? It shouldn't for our variant but hey we gotta start somewhere.
 
U may b pushing volume up instead of volume down .

Yeah I was pressing the vol down and power.


It sounds like the flash didn't work and you still have the factory recovery installed. Have you tried the Reboot Recovery command to see if that works? It shouldn't for our variant but hey we gotta start somewhere.

Don't get me wrong it's a pretty decent recovery and better than other touch recoveries I've used for my optimus elite (RIP) but I will re-root and re-install the recovery another time. Hopefully we can get CM11 or Slimkat soon.
 
Yeah I was pressing the vol down and power

Can you try pressing vol down, Home and power? That is what I do with the phone unplugged from the charger, to get to CWMT. Don't know why I need to do that now, but it works for me. It's the same method as my old Optimus V.
 
Well like I said before, I will retry this some other time lol. I might try making a themed rom for my phone to resemble kitkat if I have access to the proper files to do so.
 
Just out of curiosity, you did try both bin files...right? There is the zv5 firmware and then there's the zv6 version.
 
Back
Top Bottom