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

[xclusive36]

I just got one of these phones and its got twrp recovery on it the latest one so how do I get this recovery to this forum and my phone was all ready rooted

Follow the directions posted in the first post to install cwm touch

 

[roadkill42]

Follow the directions posted in the first post to install cwm touch

not what I was saying this phone is bran new has twrp pre instald and all ready rooted thought some one want this dump

 

[Superorb]

not what I was saying this phone is bran new has twrp pre instald and all ready rooted thought some one want this dump

Difficult to understand what you're trying to say, you're not making much sense.

Is there a question in there?

 

[xclusive36]

Are you saying that you want to give your phone away?

 

[roadkill42]

Are you saying that you want to give your phone away?

never mind

 

[gherkaul]

not what I was saying this phone is bran new has twrp pre instald and all ready rooted thought some one want this dump

It's probably the twrp recovery xclusive36's built that the previous owner installed. If you want you can send me a link to download the recovery image and I'll check it to see if it is.

 

[roadkill42]

how do I do that

 

[gherkaul]

Use a root file manager app on your phone. Open it and browse to [/dev/block/platform/msm_sdcc.1/by-name/] on your device. Copy the recovery file to somewhere on your external_sd. That's it, you can upload that file (image) to your cloud serves and pm me a link to download. If you don't mind grab the aboot as well. I already know what I'll find but I'd like to take a look at it too. They are both very small in size, btw.

 

[LOveWerks]

gherkaul; it's been awhile. Tried some scripts in SManager and, following AndroidGuy1991's script - I managed to turn my external sd into my internal, and, vice versa. An errant push of a remount button in Link2SD Plus sent this thing back to factory once again, with root retained. I have SUPERSU Pro; if I unroot this phone using SUPERSU, and SUPERSU disappears, like it said it would - could I upgrade to v8, leaving the recovery stock... and, maybe, with a re-root - get some of the flashing/nandroid/stuff that could make things work with this Beast Mobile F3? Just hoping... LW

 

[gherkaul]

gherkaul; it's been awhile. Tried some scripts in SManager and, following AndroidGuy1991's script - I managed to turn my external sd into my internal, and, vice versa. An errant push of a remount button in Link2SD Plus sent this thing back to factory once again, with root retained. I have SUPERSU Pro; if I unroot this phone using SUPERSU, and SUPERSU disappears, like it said it would - could I upgrade to v8, leaving the recovery stock... and, maybe, with a re-root - get some of the flashing/nandroid/stuff that could make things work with this Beast Mobile F3? Just hoping... LW

Hey LW, good to hear from you. All indications from testing show that it should work. I can not guarantee it though knowing how your particular phone has been acting. If you ARE successful the update will overwrite the cwm recovery with LG's stock e3 recovery. So you'll have to re-install cwm after re-rooting with Stump. Good luck, my friend.

 

[LOveWerks]

gherkaul, even with all that it has been through, it still works. I can't access my mp3s presently, but, everything else still does what it's supposed to do. The mp3 problem was my fault - I deleted the wrong music app with No Bloat Free... I'll keep you updated, and thank you for your honesty and support. LW

 

[gherkaul]

gherkaul, even with all that it has been through, it still works. I can't access my mp3s presently, but, everything else still does what it's supposed to do. The mp3 problem was my fault - I deleted the wrong music app with No Bloat Free... I'll keep you updated, and thank you for your honesty and support. LW

Yeah, you gotta watch those Bloat remover scripts and lists. Some go way to far on what they say you can remove. Just remember you gain no more storage room for your personal apps. The [system/app] folder is only for Android. The [data/app] is for you and me. However it does stop wasted resources for those apps to run in the background. Thanks for keeping me in the loop. I like to know how things are going with you.

 

[LOveWerks]

Hey LW, good to hear from you. All indications from testing show that it should work. I can not guarantee it though knowing how your particular phone has been acting. If you ARE successful the update will overwrite the cwm recovery with LG's stock e3 recovery. So you'll have to re-install cwm after re-rooting with Stump. Good luck, my friend.

gherkaul, I only have one concern: my problems started when I tried to follow sammyz's directions on the CWMT 6.0.4.8 install, which killed the stock recovery back in v6. sammyz I have no problems with, but, if I run into the same thing with v8, then, CWM or TWRP won't work, either if the same thing happens with the e3 recovery... unless, someone out there knows something that I do not... I'll keep you posted either way, gherkaul - LW

 

[LOveWerks]

Well, at least the phone didn't lock up at an LG logo screen... but, there is no root, and, CWMT v6.0.4.8 booted up right after the v8 OTA attempt. So, in effect, (after unrooting the phone at SuperSU Pro) I've got to get some .zip files into the phone right now. If you read this, PM me... this phone has been incorrigible.... :banghead: LW

 

[gherkaul]

Well, at least the phone didn't lock up at an LG logo screen... but, there is no root, and, CWMT v6.0.4.8 booted up right after the v8 OTA attempt. So, in effect, (after unrooting the phone at SuperSU Pro) I've got to get some .zip files into the phone right now. If you read this, PM me... this phone has been incorrigible.... :banghead: LW

Sent you a pm.

 

[gherkaul]

I've updated the OP with the Bump'd recovery image. This means new installation instructions are also included to reflect the change. This will make it much easier to flash the custom recovery to your device. There is no need to make any changes if you know you have the zv5 aboot installed for loki to work. Bump works with any aboot. Btw, entry into recovery mode is still key-combo.

 

[xclusive36]

I've updated the OP with the Bump'd recovery image. This means new installation instructions are also included to reflect the change. This will make it much easier to flash the custom recovery to your device. There is no need to make any changes if you know you have the zv5 aboot installed for loki to work. Bump works with any aboot. Btw, entry into recovery mode is still key-combo.

It will be a bit before i can update the stock roms. Im focused on the cm rom at the moment. If you install any rom after updating cwm, the recovery image wont be affected. Its ok to mix loki roms with the bumped cwm

 

[gherkaul]

It will be a bit before i can update the stock roms. Im focused on the cm rom at the moment. If you install any rom after updating cwm, the recovery image wont be affected. Its ok to mix loki roms with the bumped cwm

Yes it's ok. Because Bump works with all aboot versions. That's one of the great thing about it. Of course there is no need to bump a stock image. It has the LG authentication for secure boot in place. But if you modify boot/recovery you'll need to bump it so it passes the security inspection.

 

[xclusive36]

Yes it's ok. Because Bump works with all aboot versions. That's one of the great thing about it. Of course there is no need to bump a stock image. It has the LG authentication for secure boot in place. But if you modify boot/recovery you'll need to bump it so it passes the security inspection.

Thats not quite true. I had to loki the stock boot images to flash with the roms. Otherwise it would result in a security error durring boot

 

[gherkaul]

Thats not quite true. I had to loki the stock boot images to flash with the roms. Otherwise it would result in a security error durring boot

I stand corrected, my friend. So all you need to do is bump them instead of patching them with loki now. No more zv5 aboot needed. Man, I'm so glad to get away from making sure it's in place for kernel mods to work.

 

[robaho]

I stand corrected, my friend. So all you need to do is bump them instead of patching them with loki now. No more zv5 aboot needed. Man, I'm so glad to get away from making sure it's in place for kernel mods to work.

with bumped cwm can you boot into recovery using adb without wiping data?

 

[gherkaul]

with bumped cwm can you boot into recovery using adb without wiping data?

No, unfortunately we still have to use the key combo to enter custom recoveries safely.

 

[LOveWerks]

Two days ago, I went through ES File Explorer, and got rid of anything that had CWM written in it. I went through everything I could find, and the only folder that showed up for recovery was TWRP (my last attempt at getting a recovery working in this Boost Mobile phone). I wanted to make sure that I was clear to be able to OTA v8, which had been popping up at the most inopportune times.

I should've left the phone at v7. At least, it was working.

I went and unrooted the phone using SuperSU Pro, and, after cleaning out everything related to CWM, I thought I had it. I remembered falling asleep, after doing all of this.

I woke up to a phone stuck in CWMT 6.0.4.8. I started checking everything out in CWMT, and noticed a sideload function; since, you can't access the phone's internal and external SD while in this mode when hooked to the laptop. I spent most of yesterday Googling sideloading with this particular phone, and anything that pulled up was G6, or whatever.

I've even personally asked for help here. No takers.

Now, my fiancee is angry with me, since this was the only working phone that we have. My experience in bringing root to Android phones started back in the days of Gingerbread. I successfully brought root to HTC EVO 4Gs, 3VOs, and a Samsung Galaxy Prevail.

I should've researched Boost Mobile's version of the LS720...

I am so angry with myself :banghead: if anyone could spend the time in helping me get this phone back to a version of v7 that I found at LiteStep via sideload, I would be eternally grateful. I've never done this before, don't know any command prompts in Windows 8.1, and, I'm completely at sea. Looking back, we should've spent more money on a getting a phone with 4G capability.

Looking back - once again - I should've never brought root to this phone. If it was a VM, T-Mobile, or Sprint version... definitely. I didn't know about this phone's read-only sdext2, and when I first had problems with the phone back during v6, I should've left it alone.

I am very disheartened. Anyone willing to assist me would be praised with fervor within these forums.

Thank you. LW

 

[Superorb]

^^ This should help.

http://androidforums.com/virgin-mob...-did-v8-update-killed-her-phone-now-what.html

 

[LOveWerks]

Superorb, thank you for the directions to the other posts... but, my phone is stuck in CWMT 6.0.4.8, and, I can't retrieve files of any kind unless I have them on my laptop, and do a sideload... (the phone won't leave CWMT, whether I hit reboot, and it then asks for root - which I removed with SuperSU...) is there anyone out there willing to help a fellow Androidite who made the mistake of bringing root to a read/only Boost Mobile LG F3? My fiancee is upset... I'm running short on sleep... damn it, I should've never taken the root out, and stayed with v7... then, add FOTAKILL... but this is all news that happens to anyone foolish enough to bring root to a read-only Boost Mobile LG F3... I was so STUPID :banghead: