[SOLVED] Lg optimus g help required

Status
Not open for further replies.

salman09

Proficient
Jul 24, 2010
846
0
21
Lahore
So Guyz its been 2 years since am using this phone completely satisfied other than the camera khair I bought this phone 2 years back it had JELLY BEAN then I didnt mess up with it and used it in the same manner for the last 2 years now I want to play with it and update it to the latest stable ROM available
The Phone is LG Optimus G F180 already rooted with some english ROM installed

The problem is I dont have any prior experience with rooting and stuff and I need your help regarding that with step by step procedure

Every tutorial I have searched for they start from the rooting, where should I start from
Guyz am new with this stuff so provide me with the relevant information so I dont mess up my phone

Thanks
 

rusty47

Bethrezen
Aug 26, 2010
339
0
21
Karachi
www.coroflot.com
As you said your phone is already rooted! so skip the rooting part! and move to the recovery! check if your phone already have a working recovery mode! TWRP or CW. if not! get the recovery mode working! and thn move to the flashing rom! easy pizy!! :D
 

murtaza12

Global Moderator
Global Mod
Oct 27, 2011
10,755
126
69
If your phone is already rooted, with a custom ROM installed, you will definitely have a custom recovery already.

Now, since F180 is the Korean variant, CM was never officially developed for it. However, with a bit of tinkering, you can probably get the E975 build to work on the F180.

HERE is the link for Official CM for LG E975, download the latest build.
Use a Zip extractor like 7Zip to open the file, open the following directory:

META-INF\com\google\android\updater-script

Open the updater script file with notepad, delete the line starting with:

assert (getprop. (x until the last semicolon.

Here are the lines copied from the updater script from a Moto G:

Spoiler: show
assert(getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032" || getprop("ro.build.product") == "xt1032" || getprop("ro.product.device") == "xt1033" || getprop("ro.build.product") == "xt1033" || getprop("ro.product.device") == "xt1034" || getprop("ro.build.product") == "xt1034" || getprop("ro.product.device") == "falcon_umts" || getprop("ro.build.product") == "falcon_umts" || getprop("ro.product.device") == "falcon_umtsds" || getprop("ro.build.product") == "falcon_umtsds" || getprop("ro.product.device") == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma" || getprop("ro.product.device") == "falcon_retuaws" || getprop("ro.build.product") == "falcon_retuaws" || getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || getprop("ro.product.device") == "falcon_gpe" || getprop("ro.build.product") == "falcon_gpe" || abort("This package is for device: xt1031,xt1032,xt1033,xt1034,falcon_umts,falcon_umtsds,falcon_cdma,falcon_retuaws,falcon,falcon_gpe; this device is " + getprop("ro.product.device") + "."););
assert(getprop("ro.bootloader") == "0x4118" || getprop("ro.bootloader") == "0x4119" || getprop("ro.bootloader") == "0x411A" || abort("This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader " + getprop("ro.bootloader") + "."););


Delete these lines from the updater-script, save it, then close the zip file.
Copy it on to the internal storage of your phone.

Power off, boot into recovery.
Make a FULL SYSTEM backup.
Power on your phone, copy the backup folder from your phones internal storage.

Go back to recovery, wipe data/cache and factory reset.
Then flash the ROM that you copied to the phone.
Flash the correct Gapps package (I recommend OpenGapps), then wipe cache again and reboot.
You should have a fully working CyanogenMod 12.1 ROM on your phone.
 

salman09

Proficient
Jul 24, 2010
846
0
21
Lahore
If your phone is already rooted, with a custom ROM installed, you will definitely have a custom recovery already.

Now, since F180 is the Korean variant, CM was never officially developed for it. However, with a bit of tinkering, you can probably get the E975 build to work on the F180.

HERE is the link for Official CM for LG E975, download the latest build.
Use a Zip extractor like 7Zip to open the file, open the following directory:

META-INF\com\google\android\updater-script

Open the updater script file with notepad, delete the line starting with:

assert (getprop. (x until the last semicolon.

Here are the lines copied from the updater script from a Moto G:

Spoiler: show
assert(getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032" || getprop("ro.build.product") == "xt1032" || getprop("ro.product.device") == "xt1033" || getprop("ro.build.product") == "xt1033" || getprop("ro.product.device") == "xt1034" || getprop("ro.build.product") == "xt1034" || getprop("ro.product.device") == "falcon_umts" || getprop("ro.build.product") == "falcon_umts" || getprop("ro.product.device") == "falcon_umtsds" || getprop("ro.build.product") == "falcon_umtsds" || getprop("ro.product.device") == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma" || getprop("ro.product.device") == "falcon_retuaws" || getprop("ro.build.product") == "falcon_retuaws" || getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || getprop("ro.product.device") == "falcon_gpe" || getprop("ro.build.product") == "falcon_gpe" || abort("This package is for device: xt1031,xt1032,xt1033,xt1034,falcon_umts,falcon_umtsds,falcon_cdma,falcon_retuaws,falcon,falcon_gpe; this device is " + getprop("ro.product.device") + "."););
assert(getprop("ro.bootloader") == "0x4118" || getprop("ro.bootloader") == "0x4119" || getprop("ro.bootloader") == "0x411A" || abort("This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader " + getprop("ro.bootloader") + "."););


Delete these lines from the updater-script, save it, then close the zip file.
Copy it on to the internal storage of your phone.

Power off, boot into recovery.
Make a FULL SYSTEM backup.
Power on your phone, copy the backup folder from your phones internal storage.

Go back to recovery, wipe data/cache and factory reset.
Then flash the ROM that you copied to the phone.
Flash the correct Gapps package (I recommend OpenGapps), then wipe cache again and reboot.
You should have a fully working CyanogenMod 12.1 ROM on your phone.
How do I make sure that it is not already converted to international version?

Plus any detailed tutorial for converting it into international version

Sent from my LG-F180 using Tapatalk
 

murtaza12

Global Moderator
Global Mod
Oct 27, 2011
10,755
126
69
How do I make sure that it is not already converted to international version?

Plus any detailed tutorial for converting it into international version

Sent from my LG-F180 using Tapatalk
The tutorial I gave WAS for 'converting' to E975 International model.

Your phone is still running an F180 ROM.

I gave you instructions on how to edit the CM12.1 file for E975 and flash it on your F180.
 

salman09

Proficient
Jul 24, 2010
846
0
21
Lahore
If your phone is already rooted, with a custom ROM installed, you will definitely have a custom recovery already.

Now, since F180 is the Korean variant, CM was never officially developed for it. However, with a bit of tinkering, you can probably get the E975 build to work on the F180.

HERE is the link for Official CM for LG E975, download the latest build.
Use a Zip extractor like 7Zip to open the file, open the following directory:

META-INF\com\google\android\updater-script

Open the updater script file with notepad, delete the line starting with:

assert (getprop. (x until the last semicolon.

Here are the lines copied from the updater script from a Moto G:

Spoiler: show
assert(getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032" || getprop("ro.build.product") == "xt1032" || getprop("ro.product.device") == "xt1033" || getprop("ro.build.product") == "xt1033" || getprop("ro.product.device") == "xt1034" || getprop("ro.build.product") == "xt1034" || getprop("ro.product.device") == "falcon_umts" || getprop("ro.build.product") == "falcon_umts" || getprop("ro.product.device") == "falcon_umtsds" || getprop("ro.build.product") == "falcon_umtsds" || getprop("ro.product.device") == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma" || getprop("ro.product.device") == "falcon_retuaws" || getprop("ro.build.product") == "falcon_retuaws" || getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || getprop("ro.product.device") == "falcon_gpe" || getprop("ro.build.product") == "falcon_gpe" || abort("This package is for device: xt1031,xt1032,xt1033,xt1034,falcon_umts,falcon_umtsds,falcon_cdma,falcon_retuaws,falcon,falcon_gpe; this device is " + getprop("ro.product.device") + "."););
assert(getprop("ro.bootloader") == "0x4118" || getprop("ro.bootloader") == "0x4119" || getprop("ro.bootloader") == "0x411A" || abort("This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader " + getprop("ro.bootloader") + "."););


Delete these lines from the updater-script, save it, then close the zip file.
Copy it on to the internal storage of your phone.

Power off, boot into recovery.
Make a FULL SYSTEM backup.
Power on your phone, copy the backup folder from your phones internal storage.

Go back to recovery, wipe data/cache and factory reset.
Then flash the ROM that you copied to the phone.
Flash the correct Gapps package (I recommend OpenGapps), then wipe cache again and reboot.
You should have a fully working CyanogenMod 12.1 ROM on your phone.
The GApps package comes separately with its own zip file or its embedded in the build file I have downloaded?
 

salman09

Proficient
Jul 24, 2010
846
0
21
Lahore
How do I make sure that it is not already converted to international version?

Plus any detailed tutorial for converting it into international version

Sent from my LG-F180 using Tapatalk
I did what you said now I get the following error at the bootup process
Secure: booting error
Cause: boot certificate only
 

salman09

Proficient
Jul 24, 2010
846
0
21
Lahore
If your phone is already rooted, with a custom ROM installed, you will definitely have a custom recovery already.

Now, since F180 is the Korean variant, CM was never officially developed for it. However, with a bit of tinkering, you can probably get the E975 build to work on the F180.

HERE is the link for Official CM for LG E975, download the latest build.
Use a Zip extractor like 7Zip to open the file, open the following directory:

META-INF\com\google\android\updater-script

Open the updater script file with notepad, delete the line starting with:

assert (getprop. (x until the last semicolon.

Here are the lines copied from the updater script from a Moto G:

Spoiler: show
assert(getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032" || getprop("ro.build.product") == "xt1032" || getprop("ro.product.device") == "xt1033" || getprop("ro.build.product") == "xt1033" || getprop("ro.product.device") == "xt1034" || getprop("ro.build.product") == "xt1034" || getprop("ro.product.device") == "falcon_umts" || getprop("ro.build.product") == "falcon_umts" || getprop("ro.product.device") == "falcon_umtsds" || getprop("ro.build.product") == "falcon_umtsds" || getprop("ro.product.device") == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma" || getprop("ro.product.device") == "falcon_retuaws" || getprop("ro.build.product") == "falcon_retuaws" || getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || getprop("ro.product.device") == "falcon_gpe" || getprop("ro.build.product") == "falcon_gpe" || abort("This package is for device: xt1031,xt1032,xt1033,xt1034,falcon_umts,falcon_umtsds,falcon_cdma,falcon_retuaws,falcon,falcon_gpe; this device is " + getprop("ro.product.device") + "."););
assert(getprop("ro.bootloader") == "0x4118" || getprop("ro.bootloader") == "0x4119" || getprop("ro.bootloader") == "0x411A" || abort("This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader " + getprop("ro.bootloader") + "."););


Delete these lines from the updater-script, save it, then close the zip file.
Copy it on to the internal storage of your phone.

Power off, boot into recovery.
Make a FULL SYSTEM backup.
Power on your phone, copy the backup folder from your phones internal storage.

Go back to recovery, wipe data/cache and factory reset.
Then flash the ROM that you copied to the phone.
Flash the correct Gapps package (I recommend OpenGapps), then wipe cache again and reboot.
You should have a fully working CyanogenMod 12.1 ROM on your phone.
thanks alot done with it
 
Status
Not open for further replies.
General chit-chat
Help Users
We have disabled traderscore and are working on a fix. There was a bug with the plugin | Click for Discord
  • No one is chatting at the moment.
  • C chamir44:
    My withdraw
    Link
  • Necrokiller Necrokiller:
    Reminds me of the time MS tried to charge PC gamers for online play
    Link
  • Necrokiller Necrokiller:
    When will console companies realize this sh*t doesn't work on PC
    Link
  • SolitarySoldier SolitarySoldier:
    doesn't change the fact that sony is extra chu this gen
    Link
  • Link
  • StrikerX StrikerX:
    Mofos sharpened a spear and shoved it up theirs and Arrowhead's ass
    Link
  • StrikerX StrikerX:
    Sony <3
    Link
  • Necrokiller Necrokiller:
    Jeez, throwing all those sales away for the sake of PsN accounts. What a mess.
    Link
  • Link
  • Chandoo Chandoo:
    faraany3k said:
    I have heard that it is now unplayable in countries which do not support handful of third world countries not recognized by Sony like Pakistan. Steam is a true global platform.Then they cry that console gaming is dying.
    170 + countries where Steam sells but PSN doesn't will lose access unless they use VPN
    Link
  • Chandoo Chandoo:
    It has a worst rating on Steam than last years MW3 now. Jeese Sony, how can you fuck it up THIS BAD
    Link
  • faraany3k faraany3k:
    I have heard that it is now unplayable in countries which do not support handful of third world countries not recognized by Sony like Pakistan. Steam is a true global platform.Then they cry that console gaming is dying.
    Link
  • Chandoo Chandoo:
    How to ruin a perfectly good thing for dummies - by Sony
    Link
  • Link
  • Chandoo Chandoo:
    Helldivers 2 is now trending worse stream user reviews than SUICIDE SQUAD
    Link
  • Necrokiller Necrokiller:
    Good guy Gaben refunding the game way past what the policy allows 👍
    Link
  • Necrokiller Necrokiller:
    Poor Arrowhead getting screwed by Sony 😞
    Link
  • Necrokiller Necrokiller:
    Gaben ki reach hai, PSN ki nahi hai. Gaben ain't stressing over publishers who rush to his store in the first place 😂
    Link
  • Chandoo Chandoo:
    Gaben ki reach nah hai :(
    Link
  • Chandoo Chandoo:
    saeen I don't think the PSN teams are stressing over needing to offer hundreds of thousands of refunds lol
    Link
  • Necrokiller Necrokiller:
    fuckin' lol
    Link
  • Necrokiller Necrokiller:
    Saeen literally glossed over the fact that PSN isn't available in those 177 countries
    Link
  • Chandoo Chandoo:
    fuckin' lol
    Link
  • Chandoo Chandoo:
    Helldivers 2 delisted on Steam from 177 countries
    Link
  • Necrokiller Necrokiller:
    iampasha said:
    Alan wake 2 is yet to recover it's development costs. Due to no physical release and no steam launch.
    You reap what you sow. This is what happens when you take away choice from consumers. Even with 88% split going to developers, they can't recoup costs. Meanwhile, Helldivers 2 is a massive hit for Sony thanks in big part to Steam.
    Link
    C chamir44: My withdraw