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

Root Bring LG Motion ICS Rom to Connect?

pcflip

Well-Known Member
It appears that the LG motion is the connect but with a smaller different screen does that mean there is a chance of using its ICS rom and making some tweaks to bring it over to the connect?
 
i hope so but i dont think anyone can give you a 100% just yet. lets hope pg can do the job, only thing is the lg launcher on the motion is ugly in my opinion would like plain ics
 
PG where you at? XD lmao. But in all actuality, if everything is close enough, hopefully we can get that sweet, sweet sandwich.
 
Unfortunately the motion n connect are not the same as we all thought. The Motion has a different processor in it. The Connect is a msm8660 and the Motion is a msm8960.
 
well thats a bummer, so a different cpu really makes that much of a difference I mean dont they all have to operate to the same instruction sets?

*sigh* oh well, wish the motion had a 4" screen then I would have switched over.
 
well thats a bummer, so a different cpu really makes that much of a difference I mean dont they all have to operate to the same instruction sets?

*sigh* oh well, wish the motion had a 4" screen then I would have switched over.
I'm not saying it cant be ported over, but I dont do dirty ports, so I dont know what the requirements are to be able to do or not lol
 
okay thats something I have been curious about you say dirty ports? so a dirty port is when you try to make one rom work for another phone but how does that differ from say making CM work with a different device? is it because all the files and what not is available to make a new CM rom? just curious
 
okay thats something I have been curious about you say dirty ports? so a dirty port is when you try to make one rom work for another phone but how does that differ from say making CM work with a different device? is it because all the files and what not is available to make a new CM rom? just curious
Dirty Port is my definition of porting a ROM built for one device to a different device. Basically swapping files out from a existing zip etc etc, aka cooked, winzipkings, etc. ;)

verses

Built/compiled, being built from source for the specific device.

;)
 
Dirty Port is my definition of porting a ROM built for one device to a different device. Basically swapping files out from a existing zip etc etc, aka cooked, winzipkings, etc. ;)

verses

Built/compiled, being built from source for the specific device.

;)

Dirty ports are always fun xD and a lot easier than building a rom BUT you can't port anything without a rom built first really.

The only thing you could do if a stock rom existed for Motion is try to flash it and pray you don't brick........you can't dirty port ICS if you don't already have ICS built for your device!

But there is an exception, which would be same model numbers. For example: the optimus C and Optimus M model numbers are LW690 and MS690 respectively.

LW690-carrier specified number (LW)=MS690-carrier specified number (MS)

The phones are identical in every hardware possible way, but firmware is different based on carrier.

There are more exceptions based on firmware flashed to phones from phones that are different, but similar that I'm not going to get into because it's very confusing unless you did it yourself already...
 
I mentioned this is another thread, but the LG Viper is the equivalent to the Connect and they have an ICS update on the LG Open Source site, if someone can point me in the direction of how to do a "dirty port" I'd be more than happy to try it out and test it to try and bring ICS to the Connect.
 
I mentioned this is another thread, but the LG Viper is the equivalent to the Connect and they have an ICS update on the LG Open Source site, if someone can point me in the direction of how to do a "dirty port" I'd be more than happy to try it out and test it to try and bring ICS to the Connect.
yea the src is almost useless (I replied to your other post) except for the kernel src. The kernel src does include a defconfig for mpcs_us, but it wont compile as is, but then again neither will the one for the viper either. lol
 
yea the src is almost useless (I replied to your other post) except for the kernel src. The kernel src does include a defconfig for mpcs_us, but it wont compile as is, but then again neither will the one for the viper either. lol

I actually was able to compile that viper kernel after fixing LGs errors :p
 
Also, the motion and connect have nothing in common besides both being from LG. The Motion has msm8960/S4 chipset and the Connect has a msm8660/S3 chipset. ;)
 
Back
Top Bottom