1. Are you ready for the Galaxy S20? Here is everything we know so far!

[Virgin Mobile/Sprint] CWM Recovery Help Please

Discussion in 'Android Devices' started by macgoddess, Nov 4, 2014.

  1. macgoddess

    macgoddess Lurker
    Thread Starter

    So, I attempted to install the nandroid backup I made with CWM Recovery. I successfully booted up in recovery mode by using the volume down and power button. There was no choice to back up, only update from external sd card. So, I chose that and tried navigating to where my backup is saved, but I can get to the folder only, there is no file there. Of course, because it is wanting to "update" not backup, so it's looking for a zip file to update or something I guess. I have not done the v8 update yet, I keep just hitting later, could the above be because the update has downloaded to my phone? Also, is there any reason why I can't just do a factory reset and start all over? I never was able to re-install Maps to my phone, so I wanted to do whatever to get that back before dealing with the update--either install my nandroid backup (which I think I did before I lost Maps) or factory reset. I apologize for my poor terminology and hope this isn't too confusing. Thanks, guys.
     



    1. Download the Forums for Android™ app!


      Download

       
  2. macgoddess

    macgoddess Lurker
    Thread Starter

    Good to know, thank you. And should I remove my external sd card before doing so? I don't want to erase what's on it. I use link2SD, and I'm not sure how to deal with that...what is the best way to handle this?

    Since this is my first android phone, I'm trying hard to learn my way around it, (because you know I'm gonna mess with it regardless...) and so I still want to know why CWM Recovery is showing the option to update from sd card, and there is no option to backup. I mean, what if I wanted to use my backup instead of resetting? ;)

    Thank you again.
     
  3. gherkaul

    gherkaul Android Enthusiast

    From what you've described, it sounds like you're booting into the LG stock recovery (e3) not cwm. Try re-installing cwm first and see if that doesn't solve the problem.

    I'm currently working on a modified version of the zv8 ota that you flash in cwm. It maintains root after the update to 8 too. I need some brave souls to test it. It shouldn't be to dangerous, lol. Let me know if your're interested. :D
     
    NeoZiggy likes this.
  4. sandix

    sandix Android Enthusiast

    Doesn't xclusive36 already have that though? And I'd test for you if you like!
     
  5. gherkaul

    gherkaul Android Enthusiast

    He couldn't get the ifelse statement to work on the zv7 version back when bkttk2, xclusive36 and I where working on the update. So since he decided not to make one for the zv8 ota, I figured I would. I have the script look for missing files like bloatware that has been removed. Normally that would cause the update to fail. With the statement; if it's there patch it, if not move on to the next file. Xclusive left out the radio image as well, I didn't. Everything is stock and updated to the new firmware. Except for any bloat removed or running one of my themes. After flashing in cwm or twrp recovery, you are given the option to fix root. And yes your welcome to try it.
     
    NeoZiggy likes this.
  6. sandix

    sandix Android Enthusiast

    Amazing! PM me a link and ill happilybtry it out!
     
  7. gherkaul

    gherkaul Android Enthusiast

    Sent...:)
     
  8. robaho

    robaho Well-Known Member

    the problem with his ifelse was he was using == 1 instead of == 0
     
  9. gherkaul

    gherkaul Android Enthusiast

    I did not use an equivalent condition. I used the apply_patch_check as the condition with the outcome being apply_patch (true) or print the name of the missing file (false).
     
  10. NetSpeedZ

    NetSpeedZ Android Enthusiast

    I would be interested in testing - especially since 4G quit running on my phone and I decided to restore a backup and the backup didn't go. Error with data.

    Anyway, if you PM me a link, I'll try it.

    ------------
     
  11. gherkaul

    gherkaul Android Enthusiast

    I'm going to try and post it soon. Just haven't had the time to write up a proper guide with all the info yet. Making a few more tweaks too. I'll send you a copy if you promise me to send me your results. I haven't heard back from anyone I've already sent it out to yet. It's hard to know if there are any issues or problems if nobody gives me feedback on how it worked. ;) I like to make sure my mod's are as safe as possible before releasing them...know what I mean.
     
    NeoZiggy likes this.
  12. NetSpeedZ

    NetSpeedZ Android Enthusiast

    Copy that. I'm a software developer myself and know the importance of good feedback.

    ------------
     
  13. NeoZiggy

    NeoZiggy Android Enthusiast

    I'll give it a go. I've removed some bloat and froze a lot of apps. Could be good fot testing the install.
     
  14. NeoZiggy

    NeoZiggy Android Enthusiast

    I meant I'll test the modded v8 update... lol
    If that was meant for the OP, my bad. :x
     
  15. gherkaul

    gherkaul Android Enthusiast

    Just got home from work. I'll send you a link in a little while.
     
  16. robaho

    robaho Well-Known Member

    be very careful here... the v8 update has a radio image update that includes an aboot image update.

    I ran mine manually and then installed the version 5 aboot otherwise the aboot could detect a non VM boot image and refuse to boot bricking the device. essentially blocking Loki.

    I would modify the update to include the v5 aboot update in the radio image (not sure if this is easy...) or just install it as part of the update (I had problems doing this as part of the script... I think the update radio image command causes the script to terminate)

    just beware....
     
  17. gherkaul

    gherkaul Android Enthusiast

    I tried that too. But installing the zv5 aboot did cause a brick. A nasty one at that...twice. I have not encountered any problem so far not including it. You do have to re-install your custom recovery. The zv5 aboot flashs (ES copy) fine and they all have it except PG's. The only thing this mod does different then the original is continue if bloatware or one of my themes are installed. Before of course the update would fail the assert argument. That argument change to ifelse only effects those files. The rest still have to pass but those no one needs to be fooling with if they're still on the factory stock firmware.

    Any thoughts on why flashing the zv5 aboot would cause a hard brick. I put it last in the script. After the radio flashes the new aboot. On reboot the screen goes blank and bam it's hard-bricked. Listen, I know the difference between a soft and hard brick, as well as what can cause both. I just can't figure out why flashing it, does.
     
  18. robaho

    robaho Well-Known Member

    I have the v5 aboot installed with my previous oc kernel. it is working fine for me. not sure why you're having a problem unless the v5 aboot can't boot the provided v8 kernel... lg has not released the source for the v8 kernel so I can't determine what they've changed. my v5-v7 kernels work fine with the v5 aboot and the v8 update.

    also, be careful with allowing the update if some framework files have changed (custom ui etc) this can cause a v8 odexed apk to randomly fc when using an outdated framework file, usually this is safe or they would need to update ALL system apks.
     
  19. gherkaul

    gherkaul Android Enthusiast

    Thank for replying so quickly. I truly appreciate your input and your thoughts on this subject. Will be looking forward to your next kernel. Would it be possible for you to add the Trim technology to our kernel like GameTheory did with his Freedom kernel for the T-M/Metro f3 variant? ;)
     
    sandix likes this.

LG Optimus F3 Forum

The LG Optimus F3 release date was June 2013. Features and Specs include a 4.0" inch screen, 5MP camera, 1GB RAM, Snapdragon 400 processor, and 2460mAh battery.

June 2013
Release Date
0
Reviews
Loading...

Share This Page

Loading...