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

Root [ROM] CyanogenMod 7 for the LG Optimus M MS690

dogdayz said:
You could flash the plague kernel first then then the rom plus dont 4get the gapps that's how it worked for me.
Click to expand...


wouldn't you have to have a flashed rom first b4 flashing the plague kernel? without no rom on the phone :confused: It'll be crazy to redo everything i have over like 100 apps installed.
 
dogdayz said:
Well make a back up lol it does work try it if you want to make sure you flash like this
do the wipes
*plague
*cm7
*gapps
within the recovery!
I got mine OC @768 :)
Click to expand...

Kool im going to try it in a bit after i backup everything. But hold on i already flashed it twice thinking it did not do anything wouldn i have to ust redo cm7 and gapps now? lol
 
alright ill let u know later on if it went well, hey i added you on gtalk just in case i needed some help.
 
dogdayz said:
Cool....
Click to expand...

Ok i re did everything as you said, Plague kernel>CM7>gapps. Now how do you actually know its actually there/installed, i wasent able to apply any number with the on demand option, phone went crazy on me no matter what i picked. System was like a huge COD Glitch LMAO:D

BTW: the only option that actually let me choose was Performance with a reboot.
 
dogdayz said:
Lol it did the same to me I didn't switch the governor I left it the same I started 4rm 600 worked my way to 768.
Did you set on smartassV2???
Click to expand...

im gonna go ahead and try it, did u use the cm7 changer or did you use an app like SetCPU?


ok now im in smartassv2 with 768Mhz but im still noticing a bit of glitching whenever i got threw menus and stuff.
 
Yes I am a noob.. Got a question tho, I have a LG Optimus MS690, running CM7.2 with Plague kernel, I have it overclocked @ 748. Everything is running awesome.. acouple hick ups though.

1) the camera is upsidedown
2) the battery drains soo fast even with everything turned off and not overclocked.
3) my phone now says its a LG LW690 (Cricket), although everything works fine.

so my question is.. is that normal for this ROM? No matter what, I'd rather be using this mod instead of the stock rom. Maybe I picked up the wrong rom, or outdated rom. I tried to use RM but I think I'll just stick to manually flashing my phone. Thank you to all the people who put effort into making this ROM!! If I wasn't so broke I would donate!!


My "About phone" says:

Model #: LG-LW690
Android ver: 2.3.5
baseband: M76XX-TSNCJPLYM-6040
Kernel: 2.6.32.9-plague
Mod Ver: CyanogenMod-7.2-LG-LW690-09082011
Build #: GRJ90 (09082011/LG-LW690)

Before I switched to Cyanogen, I was using Kelso's EasyRider(?) rom, which still said MS690.

Any tips, or anything to update (Or fix some issues) would be appreciated.

-Jason
 
dogdayz said:
Yup I'm using setCPU the glitches go away once it settles into your system.
You could run the su fix_permissions as well in the terminal
Click to expand...

alright i have setcpu but im using the cm7 internal one, ill give the permissions a fix and see.
 
jasonzech said:
Yes I am a noob.. Got a question tho, I have a LG Optimus MS690, running CM7.2 with Plague kernel, I have it overclocked @ 748. Everything is running awesome.. acouple hick ups though.

1) the camera is upsidedown
2) the battery drains soo fast even with everything turned off and not overclocked.
3) my phone now says its a LG LW690 (Cricket), although everything works fine.

so my question is.. is that normal for this ROM? No matter what, I'd rather be using this mod instead of the stock rom. Maybe I picked up the wrong rom, or outdated rom. I tried to use RM but I think I'll just stick to manually flashing my phone. Thank you to all the people who put effort into making this ROM!! If I wasn't so broke I would donate!!


My "About phone" says:

Model #: LG-LW690
Android ver: 2.3.5
baseband: M76XX-TSNCJPLYM-6040
Kernel: 2.6.32.9-plague
Mod Ver: CyanogenMod-7.2-LG-LW690-09082011
Build #: GRJ90 (09082011/LG-LW690)

Before I switched to Cyanogen, I was using Kelso's EasyRider(?) rom, which still said MS690.

Any tips, or anything to update (Or fix some issues) would be appreciated.

-Jason
Click to expand...


for the camera issue im not and expert but try running the fix_permissions and reboot or just replace the app.

for the battery, use a battery calibration app like this one that might help. This erases any misleading battery stats left from previous flashed roms, therefore letting the phone read the correct stats.

about the model name ... no idea lol
 
dogdayz said:
Hey Jason try Sammyz porting guide learn 4rm him he has a thread around here somewhere.
Click to expand...

Nononono Jason has an optimus M and he downloaded a CM7 ROM and his model # says LW690....well that must be because either he downloaded the Optimus C version of this ROM, or PlayfulGod never edited the build.prop because he overlooked it. I wouldn't worry about it. It's not important. My BACKside port for the optimus M has model# LW690 because I screwed it up... when will I fix it? When there's an update...
 
dogdayz said:
Well I ported joyOS which I called it CrazyjoyOS_optimus_C onto my phone lol
Click to expand...

How is that going, any issues?

is it possible to replace system images and things with Photoshop edited images to give it a new look although there old roms? change things up a bit. It will be so awesome to have backgrounds on the system menus as you're going threw them.
 
dogdayz said:
Well I got data working,mms is a no go, the rest of its working and stuff you mention might work.
Click to expand...

Im stacking up a few tutorials right now to learn from, that way im more prepared if i try anything. I'm installing Photoshop CS5 right now also.
 
Phubu said:
for the camera issue im not and expert but try running the fix_permissions and reboot or just replace the app.

for the battery, use a battery calibration app like this one that might help. This erases any misleading battery stats left from previous flashed roms, therefore letting the phone read the correct stats.

about the model name ... no idea lol
Click to expand...

Thanks for the advice. I'll run the battery calibration as soon as I can.
The biggest problem is the camera. If I cannot figure out why this is happening, I will need to switch rom's. I found two CM7.2's, one by Playfulgod, and the other one by BobZ. So I guess I'll flash over to Bobz's and see what happens but at last resort. I hope someone can give me a idea why this is happening. I use my camera allot. I've tried downloading other camera apps and still same result. I've tried with OverClocked and without. All still same results.

If someone has any idea or a way to fix it I would love to hear from ya.

BTW: thanks for the fast replys. You guys are really the best!! I've been only flashing/rooting phones for only 20 days now. so ya I'm a noob, but I'm getting better becuz u guys..


ya. I sound like a butt kisser but hey! I meant what I said.

Thanks,
Jason


--- UPDATE ---

Reflashed my phone with BobZ's CM7.2RC0 03242012.. Worked like A charm! It fixed the camera and everything works.. Except I cannot find the Play Store... I see the Play books and etc but no Play Store.. So I'm gonna reflash the gapps...
 
jasonzech said:
Thanks for the advice. I'll run the battery calibration as soon as I can.
The biggest problem is the camera. If I cannot figure out why this is happening, I will need to switch rom's. I found two CM7.2's, one by Playfulgod, and the other one by BobZ. So I guess I'll flash over to Bobz's and see what happens but at last resort. I hope someone can give me a idea why this is happening. I use my camera allot. I've tried downloading other camera apps and still same result. I've tried with OverClocked and without. All still same results.

If someone has any idea or a way to fix it I would love to hear from ya.

BTW: thanks for the fast replys. You guys are really the best!! I've been only flashing/rooting phones for only 20 days now. so ya I'm a noob, but I'm getting better becuz u guys..


ya. I sound like a butt kisser but hey! I meant what I said.

Thanks,
Jason
Click to expand...


Glad that you're learning quick... i'm kinda in the same boat, but we're all here to help :)
 
Phubu said:
thats exactly it.
Click to expand...

Damn, when one problem fixes, it causes atleast two more problems. Installed the gapps, worked fine. Used "Market" and installed a few things. That worked fine.. then it updated to Play Store.. Now heres the problem, every time I try to install a APK, either through play store or off my sdcard, it says "Package is invalid". What Am I doing wrong?! I'm just about to go back to Kelso's Easy Rider rom, that worked great except it was back to 2.2.2.. But I would really miss the DSP, and tweaks and more..
I used the gapps-gb-20110828-signed.zip. should I reflash it with the 20110613? Getting tired of losing all my apps and settings. oh well, the price we pay for modding it :)

---EDITED/UPDATED---

NV :) Found a way to fix it... just booted back into the recovery, wipe dalvik-cache.. worked perfectly :)

---Not Fixed---

wow.... I was able to install one app fine, then I tried another APP and its back at "Package is invalid"... WTF?!?!?! Stupid PHONES!! haha

well I guess until I find a perm fix.. I guess I could always wipe dalvik cache then install a new app or update.. hmmm this bites.
 
jasonzech said:
Damn, when one problem fixes, it causes atleast two more problems. Installed the gapps, worked fine. Used "Market" and installed a few things. That worked fine.. then it updated to Play Store.. Now heres the problem, every time I try to install a APK, either through play store or off my sdcard, it says "Package is invalid". What Am I doing wrong?! I'm just about to go back to Kelso's Easy Rider rom, that worked great except it was back to 2.2.2.. But I would really miss the DSP, and tweaks and more..
I used the gapps-gb-20110828-signed.zip. should I reflash it with the 20110613? Getting tired of losing all my apps and settings. oh well, the price we pay for modding it :)

---EDITED/UPDATED---

NV :) Found a way to fix it... just booted back into the recovery, wipe dalvik-cache.. worked perfectly :)

---Not Fixed---

wow.... I was able to install one app fine, then I tried another APP and its back at "Package is invalid"... WTF?!?!?! Stupid PHONES!! haha

well I guess until I find a perm fix.. I guess I could always wipe dalvik cache then install a new app or update.. hmmm this bites.
Click to expand...


There's a fix for that, look through BobZhome's CM7 thread, search "to fix market"
 
You must log in or register to reply here.
Back
Top Bottom