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

Root Unofficial CM7 port, inquire within.

B

blarf

Newbie
I've got a mostly functional CM7 port for the Optimus S and V, and would like to get it working with the C, M, U, and maybe Vortex. I'm looking for the following:

- An unrooted Optimus M (blocked or otherwise not activated is fine as long as it's not stolen and the phone itself works)
- Someone willing to build, distribute, more extensively test, and probably support this monstrosity.

To build, start here:

https://github.com/inferiorhumanorgans/android
 
Yeah, a hack of the abandoned 'aosp' port for the VM670. Check the list of bugs.

"Banner still says Virgin Mobile"

So yeah, camera zoom and autofocus may or may not work, MMS still needs another flash, ringtones probably play out of the wrong speaker, headsets (wired and BT) probably don't work, and so-on.
 
blarf said:
I've got a mostly functional CM7 port for the Optimus S and V, and would like to get it working with the C, M, U, and maybe Vortex. I'm looking for the following:

- An unrooted Optimus M (blocked or otherwise not activated is fine as long as it's not stolen and the phone itself works)
- Someone willing to build, distribute, more extensively test, and probably support this monstrosity.

PM if you can help out. Thanks.
Click to expand...

I can help just sent you a pm.
 
blarf said:
Yeah, a hack of the abandoned 'aosp' port for the VM670. Check the list of bugs.

"Banner still says Virgin Mobile"

So yeah, camera zoom and autofocus may or may not work, MMS still needs another flash, ringtones probably play out of the wrong speaker, headsets (wired and BT) probably don't work, and so-on.
Click to expand...

I'm working on getting a build rig up to compile my own nightlies. I'll let you know if/when I get it running, I'd be happy to assist if possible.
 
Excellent. I've just edited the first post with instructions. Let me know how it goes. Right now what I'd really like is a dump of the /system partition from a *stock* Optimus M. If anyone has a phone (unactivated/blocked but not stolen is just fine) to donate, PM me. That'd speed things up quite a bit.
 
Nope. Dunno what filesystem the Optimus M was using, but it's not yaffs (either that or the images are corrupted).
 
blarf said:
I've got a mostly functional CM7 port for the Optimus S and V, and would like to get it working with the C, M, U, and maybe Vortex. I'm looking for the following:

- An unrooted Optimus M (blocked or otherwise not activated is fine as long as it's not stolen and the phone itself works)
- Someone willing to build, distribute, more extensively test, and probably support this monstrosity.

To build, start here:

https://github.com/inferiorhumanorgans/android
Click to expand...

I was trying to build something. It went all good, but I experienced a hardware problem from my pc. Somehow my HD fried up earlier, so now I have no laptop :(

That`s just crazy. LOL

But no worries I still can work from my desktop. Hopefully I can build this rom successfully.
 
Wooooooooooooooooooooh, this is GREAT, I was waiting for this, Please Please Please, I will try to donate if this gets done successfully, Lol I've been waiting for MONTHS :DDDDD..and also I would like more info on the already created CM7, is it stable?
 
joneidy said:
I was trying to build something. It went all good, but I experienced a hardware problem from my pc. Somehow my HD fried up earlier, so now I have no laptop :(

That`s just crazy. LOL

But no worries I still can work from my desktop. Hopefully I can build this rom successfully.
Click to expand...

You'll need a kernel in the proper directory (MS690) and the appropriate kernel modules to successfully build the ROM. Then go into the device specific overlays. The eri.xml and mms.xml from a stock ROM are the big ones. The phone stuff could probably be omitted or merged into a common overlay.

Then it's off to verify that recovery.fstab (output of mount should work) and the partition sizes in BoardConfig.mk match the ***STOCK*** Optimus M.

Put this in a text file, put it in your /system directory, chmod +x it and run it.

Code: 
printf "%-4s\t%-9s\t%-9s\t%s\n" dev size erasesize name
for x in `ls -d /sys/devices/virtual/mtd/mtd?`; do
    printf "%s\t0x%07x\t0x%07x\t%s\n" `basename $x` `cat $x/size` `cat $x/erasesize` `cat $x/name`
done

And report back.

reppard said:
Opt m does use yaffs
Click to expand...

None of the versions of unyaffs I used could extract anything from the images linked above.
 
blarf said:
You'll need a kernel in the proper directory (MS690) and the appropriate kernel modules to successfully build the ROM. Then go into the device specific overlays. The eri.xml and mms.xml from a stock ROM are the big ones. The phone stuff could probably be omitted or merged into a common overlay.

Then it's off to verify that recovery.fstab (output of mount should work) and the partition sizes in BoardConfig.mk match the ***STOCK*** Optimus M.

Put this in a text file, put it in your /system directory, chmod +x it and run it.

Code: 
printf "%-4s\t%-9s\t%-9s\t%s\n" dev size erasesize name
for x in `ls -d /sys/devices/virtual/mtd/mtd?`; do
    printf "%s\t0x%07x\t0x%07x\t%s\n" `basename $x` `cat $x/size` `cat $x/erasesize` `cat $x/name`
done

And report back.



None of the versions of unyaffs I used could extract anything from the images linked above.
Click to expand...


All versions of android use this file system as far as I know. I use some bash scripts in Linux to extract these images ill see if I can dig them up.
 
reppard said:
All versions of android use this file system as far as I know. I use some bash scripts in Linux to extract these images ill see if I can dig them up.
Click to expand...

Ya I can extract the boot image with one of those scripts (I think) but not the system one where all the fun lives. Really a stock phone would be great to expedite everything. In the meantime a usable fs dump would be great.
 
blarf said:
Ya I can extract the boot image with one of those scripts (I think) but not the system one where all the fun lives. Really a stock phone would be great to expedite everything. In the meantime a usable fs dump would be great.
Click to expand...


What fun stuff are you talking about? Would the stock android source not work for you? I have already ported the optimus v cmod7 to this phone so I could probably help you out a bit. What more than porting are you wanting to achieve.
 
blarf said:
You'll need a kernel in the proper directory (MS690) and the appropriate kernel modules to successfully build the ROM. Then go into the device specific overlays. The eri.xml and mms.xml from a stock ROM are the big ones. The phone stuff could probably be omitted or merged into a common overlay.

Then it's off to verify that recovery.fstab (output of mount should work) and the partition sizes in BoardConfig.mk match the ***STOCK*** Optimus M.

Put this in a text file, put it in your /system directory, chmod +x it and run it.

Code: 
printf "%-4s\t%-9s\t%-9s\t%s\n" dev size erasesize name
for x in `ls -d /sys/devices/virtual/mtd/mtd?`; do
    printf "%s\t0x%07x\t0x%07x\t%s\n" `basename $x` `cat $x/size` `cat $x/erasesize` `cat $x/name`
done

And report back.



None of the versions of unyaffs I used could extract anything from the images linked above.
Click to expand...

Got the overlay folder all in order, including the files eri.xml and mms_config.xml.

Also got the MS690 folder setup including the kernel (zimage) and the modules (wireless.ko).

I had to modify the partition sizes because they didn`t match with the Optimus M.

But I couldnt get that file to execute, everytime I did:
Code: 
chmod +r text.txt
it said bad mode. That`s the only thing that I couldnt get.

I did
Code: 
cat /proc/mtd
and that was how I got the partition sizes

Now all I need to know what`s next. LOL
 
Ah that's where that info lives. chmod +x not +r. Can you paste the partition info? Better yet fork android_device_lge_thunderc and commit your changes. If you treat each logical group of files as a separate commit you can file a pull request, and I'll get that stuff merged in.

You got your mms.xml and such from a stock Optimus M, right?

Which kernel did you use?

Next you'll need to get the binary blobs and put them in vendor/lge/thunderc/whatever folders. If you go through device_thunderc.mk you'll see which files are needed.

Also, can you please post a stock apns-conf.xml and build.prop? Thanks.

Now you should be able to build and install it.

Building your own ROM - Android Forums
 
reppard said:
What fun stuff are you talking about? Would the stock android source not work for you? I have already ported the optimus v cmod7 to this phone so I could probably help you out a bit. What more than porting are you wanting to achieve.
Click to expand...

I'm trying to get a look at the stock binary blobs and the stock config files. I've seen the MMS patch, but I'd like to get this to the point where one can generate an MS690 build from source without having to apply a buch of patches.

The APN stuff will get submitted for inclusion to the CM repo so I'd like to make sure it's correct. If I can get my hands on a phone I'll try my hand at a custom built kernel.
 
blarf said:
Ah that's where that info lives. chmod +x not +r. Can you paste the partition info? Better yet fork android_device_lge_thunderc and commit your changes. If you treat each logical group of files as a separate commit you can file a pull request, and I'll get that stuff merged in.

You got your mms.xml and such from a stock Optimus M, right?

Which kernel did you use?

Next you'll need to get the binary blobs and put them in vendor/lge/thunderc/whatever folders. If you go through device_thunderc.mk you'll see which files are needed.

Also, can you please post a stock apns-conf.xml and build.prop? Thanks.

Now you should be able to build and install it.

Building your own ROM - Android Forums
Click to expand...

Partition Info:

Code: 
dev:    size   erasesize  name
mtd0: 00500000 00020000 "boot"
mtd1: 04340000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 0bd00000 00020000 "system"
mtd6: 0c900000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"

Yeah I got the mms_config.xml and others from a stock Optimus M. LOL

I used our Overcloked kernel created by reppard. It`s called r.O.C.K

I already went through device_thunder.mk and copied all necessary files. But I had to replace the bluetooth one because didnt match. The one called BCM....

The apns from stock are not real they are all fake, but on mms_hidden.xml I got some of it. I`ll attach the build.pro and what I got for the apns.
 

Attachments

So the file named BCM4325D1_004.002.004.0218.0248.hcd was named BCM.hcd? Or? That's your bluetooth firmware. If you change the name of it you'll have to update the init.thunderc.rc or your BT won't work.

Can you attach a listing of the system fs (adb shell find /system > system_list.txt), the apns-conf.xml, eri.xml, mms_config.xml, and the Phone.apk strings.xml (or just the Phone.apk)? Thanks.

Let me know when you've built and tried it lol. If it works, point me in the direction of the kernel and I'll add it to the repository.

Looks like otherwise most of my guesses about the MS690 were right on.
 
blarf said:
So the file named BCM4325D1_004.002.004.0218.0248.hcd was named BCM.hcd? Or? That's your bluetooth firmware. If you change the name of it you'll have to update the init.thunderc.rc or your BT won't work.

Can you attach a listing of the system fs (adb shell find /system > system_list.txt) and the apns-conf.xml? Thanks.

Let me know when you've built and tried it lol. If it works, point me in the direction of the kernel and I'll add it to the repository.

Looks like otherwise most of my guesses about the MS690 were right on.
Click to expand...

Opps my bad. My bluetooth firmware name is: BCM4235D1_004.002.004.0285.0288.hcd

So I replaced the one that was on the script with mines. But I didn`t change the init.thunderc.rc. So I`ll do that in a sec. LOL

I`m going to edit the int..thunderc.rc and I`ll start building.
Let you know what happnes
 
joneidy said:
Opps my bad. My bluetooth firmware name is: BCM4235D1_004.002.004.0285.0288.hcd

So I replaced the one that was on the script with mines. But I didn`t change the init.thunderc.rc. So I`ll do that in a sec. LOL

I`m going to edit the int..thunderc.rc and I`ll start building.
Let you know what happnes
Click to expand...

Okay, if that all works out can you fork https://github.com/inferiorhumanorgans/vendor_lge_thunderc, commit/push your binary blobs into the MS690 directory, and then file a pull request?
 
blarf said:
Any luck?
Click to expand...

Not really. In get until the point where it`s building the Mms.apk but gives an error saying mismatched tag: error parsing xml. The error says that it`s coming from the /device/lge/thunderc/overlay-MS690/packages/apps/Mms/res/xml/mms_config.xml

I dont know if it`s that the Optimus M has an option for video and the cyanogen one doesnt.

But I`m trying again without that option on the overlay-MS690 folder.
 
You must log in or register to reply here.
Back
Top Bottom