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

Root [ROOT][RECOVERY]{Touch/Non-Touch} Optimus F7 FX1

Did you make sure to hit Package Installer and not Google's Verify and install?
 
Sounds like something just simply got fudged up through natural use. Have you tried running Clean Master & Clearing data from Google Services Framework?
 
No it does not, you have to do it manually. Settings>Apps>All>Google Services Framework>Force Stop then Clear data & then reboot. Wait a few minutes then reboot again and attempt to install an app from Play Store, doesn't matter which one. After it's installed, reboot, wait for the phone to finish scanning the on board storage and external SD card for files and then attempt to install Framaroot. Also, try using the Framaroot.apk version 1.9.3 from here http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t213027
 
Glad you got that kink ironed out. Words of wisdom; always give your phone time to check itself before attempting to do anything with it. By doing so, your phone gets an identity of itself and what's it capable of doing. By not allowing your phone to run it's necessary pre-scans before you began using it, you run the risk of your phone not accessing the necessary instruction sets and you those error messages in return; your phone literally didn't know it can install outside .apk files.. This applies to all of your electronics: computer, television, cable box, iron and even your car. More and more devices are getting on board computers and they all need to do a self assessment upon boot. Simply allowing these devices a minute or two to assess themselves will prevent many hiccups such as the one you faced today. In the case of Android phones in particular, not letting the pre-scan functions to run is the number cause of headaches. Hope this helps. Happy Rooting!
 
They were, had to start over, now I can't get into google play to go through the steps you outlined above . . .
 
I've been rooted for awhile now and wanted to try a ROM. I was able to get CWM installed and a Nandroid backup saved on my SD card when I originally rooted and booted into recovery (probably a year-ish ago), but I can't reboot back into recovery now.

I get to the screen asking you to hit the power key to confirm booting into recovery, but when I hit the key, it just says "Confirmed Phone will go into Android Recovery!"...and nothing. Screen doesn't go blank, no LED - nothing. I pull the batter and try again - same result. I tried booting from an app (knowing it would wipe my data) - same result.

Any thoughts? I'm using US Cellular.
 
Is it working now thodol?

gwilgenbusch, NEVER (not shouting, it's to emphasize it's importance) try to boot into recovery from any app even a custom ROM's power button menu unless the dev of the project specifically says it's okay but Always ask first if the dev didn't explicitly say so in the notes or change log. Is the CWM ROM that you installed this http://androidforums.com/threads/rom-beta-3-unofficial-cyanogenmod-10.839551/? If not, please let us know where you got the ROM from before you attempt anything else.
 
Remember, never reboot into recovery from any app nor the CWM or PhilZ recovery. ONLY boot into recovery by holding down the VOLUME DOWN button & power button.
 
You must log in or register to reply here.
Back
Top Bottom