This something i had stumbled on accident trying to dual boot my LG G2x (p999) using the LG Optimus 2x (P990) Dual Boot tutorial.
If done correctly, your your LG G2x will be model P990 instead of P999. you will be using Optimus 2x Roms instead of G2x Roms. Everything Should you need will be on this besides the 2 roms you want to dual boot http://forum.xda-developers.com/showthread.php?t=1856090
Well... Thanks for sharing but...
The Baseband and RIL still working with the G2X??
I doubt so. I have the dual boot for the G2X it works well but even if you use the p990 files the baseban and ril would have to be for the g2x, and i doubt thing will work out. It is better to port the roms instead.
I am looking for a straightforward explanation of the file systems for the P990 and the P999 especially a comparison and, better, a utility/script that would enable selecting the one to be used to format memory. I am also looking for information about how to port between the P990 to and from the P999. Do you have it or know where any of that information is located?
Rafase282 said:
I doubt so. I have the dual boot for the G2X it works well but even if you use the p990 files the baseban and ril would have to be for the g2x, and i doubt thing will work out. It is better to port the roms instead.
Click to expand...
Click to collapse
In theory, If you were using the current March 2012 baseband (v21y), couldn't you just flash OWAIN's NewBaseband.zip, and then run GetRIL to make sure the RIL is updated to the baseband?
That should get you a working phone (in p990 mode).
New2my8125 said:
In theory, If you were using the current March 2012 baseband (v21y), couldn't you just flash OWAIN's NewBaseband.zip, and then run GetRIL to make sure the RIL is updated to the baseband?
That should get you a working phone (in p990 mode).
Click to expand...
Click to collapse
Maybe I was not clear on my post. The devices are most similar. The differences are on the radio (baseband, irl, etc), partition scheme, and the p990 has fm radio while the p999 does not. They are made for different carries so while you may be able to use those files, what they are intended to do is to change the partition scheme to allow two roms to fit, and then use some scripts to switch roms using the boot.imgs you provide and changing system, data, and other files like that to a different name so each rom has independent files, they are all store on data.
So the problem is that your radio stays the same, so by flashing the wrong baseband/radio you will just brick your phone. It can be recovered on these particular devices using nvflash but overall it should not work as just changing every entry from p999 to p990. That can be done when building the rom, just change the assertion script or turn it off and you can flash anything on the partitions given that they are the right size, it will still not work tho.
This will be really usefull when a Full stable ICS O2X rom come out...
DankoFGL said:
This will be really usefull when a Full stable ICS O2X rom come out...
Click to expand...
Click to collapse
No, when such thing comes out it will be ported, no need to change the partition scheme or anything.
Rafase282 said:
No, when such thing comes out it will be ported, no need to change the partition scheme or anything.
Click to expand...
Click to collapse
Not necessarily true! No O2X OFFICIAL Rom has ever been ported successfully to the G2X. CM7/CM9/MIUI yes, because we have source. Factory/Official ROMs? Never 100% successfully.
I had a GB O2X Rom running on my G2X once before, but I forget what I had to do to make it happen. DId nothing with KDZ's, I modded the kernel somehow. But, as others discovered, it wasn't possible to get the radio working. Curious if Owain's fix would work as a port as suggested previously in this thread.
Would be nice to have a native O2X Rom to run... I think 9/10ths of the "crazy bat**** stupid" problems the G2X has are due to the fact that LG basically stripped out LG Framework to make it appear AOSP without actually being AOSP. The problem is, they didn't strip out all of the LG Framework, only the parts that you see. So the G2X has a lot of unused and half-connected code on stock Roms.
And, as others said, it could be very useful for ICS...
But as I've said... Several of us have had O2X roms ported. The hitch has always been lack of cellular radio.
Rafase282 said:
I doubt so. I have the dual boot for the G2X it works well but even if you use the p990 files the baseban and ril would have to be for the g2x, and i doubt thing will work out. It is better to port the roms instead.
Click to expand...
Click to collapse
Is there a thread for G2X dual boot? This is the first I've heard of it, I'd hate to have to try to rewrite the O2X scripts myself, but dual boot sounds very nice.
Core Memory said:
I am looking for a straightforward explanation of the file systems for the P990 and the P999 especially a comparison and, better, a utility/script that would enable selecting the one to be used to format memory. I am also looking for information about how to port between the P990 to and from the P999. Do you have it or know where any of that information is located?
Click to expand...
Click to collapse
I hate to say it but probably the best explanation would be the compile scripts for source. From the limited research I've done(kanging the CM10 blind builds), once you build the P990/SU990 source with the P999 script, you pretty much "fill in the blanks/diff" by using a full P999 rom aka CM10 kang (somewhere I remember seeing a list of what the source doesn't include). I know someone ran df or fdisk or something of that nature on a SU990 and posted the results with the ICS rom so the differences are sorta documented....Or you could ask wkpark.I might myself as I speak and write his native language!
bakedpatato said:
I hate to say it but probably the best explanation would be the compile scripts for source. From the limited research I've done(kanging the CM10 blind builds), once you build the P990/SU990 source with the P999 script, you pretty much "fill in the blanks/diff" by using a full P999 rom aka CM10 kang (somewhere I remember seeing a list of what the source doesn't include). I know someone ran df or fdisk or something of that nature on a SU990 and posted the results with the ICS rom so the differences are sorta documented....Or you could ask wkpark.I might myself as I speak and write his native language!
Click to expand...
Click to collapse
Please ask.
Yes, you can easily dual boot ROMs with the G2X, I do it with Temaesk and my stock ROM. Very convenient. Search through the thread and there should be someone who posted the proper partitions for our phone for use with NVFlash.
If you don't know what you're doing, or are new to this stuff and don't know what the word "troubleshooting" means, then stay away from it as most of the help is for the O2X and I've semi-bricked/bootlooped my phone before I got the complete feel for dual booting it correctly and how to update kernels for it and such.
buru898 said:
Yes, you can easily dual boot ROMs with the G2X, I do it with Temaesk and my stock ROM. Very convenient. Search through the thread and there should be someone who posted the proper partitions for our phone for use with NVFlash.
If you don't know what you're doing, or are new to this stuff and don't know what the word "troubleshooting" means, then stay away from it as most of the help is for the O2X and I've semi-bricked/bootlooped my phone before I got the complete feel for dual booting it correctly and how to update kernels for it and such.
Click to expand...
Click to collapse
Isn't the partition setup in the .cfg file used with NVFlash?
I just want to simply know if it's it possible to flash any O2x rom on the G2x? I don't care if the radio isn't working, I already use my Galaxy Nexus for calling/texting etc. I just want to get a touch of ICS/Other O2x roms.
breadland said:
I just want to simply know if it's it possible to flash any O2x rom on the G2x? I don't care if the radio isn't working, I already use my Galaxy Nexus for calling/texting etc. I just want to get a touch of ICS/Other O2x roms.
Click to expand...
Click to collapse
Answering your question the answer is not. If you don't care about the radio then use the dualboot method or just properly change the partition scheme and flash your rom and let us know what happens. Since it doesnt seem to be your main phone you wont miss anything if it bricks. As far as I know our phone is "unbrickable".
Core Memory said:
Please ask.
Click to expand...
Click to collapse
I posted on daum(my name roughly translates to 'angry at butt') but I think wkpark thinks i'm some sort of script kiddie or something due to the name...hah.
I had no luck installing an O2x rom on my G2x. The nvflash part worked, but the installation part was too confusing for me so I probably did something wrong. I'm wondering if anyone actually managed to install an O2x rom on the G2x successfully.
breadland said:
I had no luck installing an O2x rom on my G2x. The nvflash part worked, but the installation part was too confusing for me so I probably did something wrong. I'm wondering if anyone actually managed to install an O2x rom on the G2x successfully.
Click to expand...
Click to collapse
No, not directly.
Help
Hello I hope someone reads this.
I have accidentally partitioned my P999 with the P990 all in one tool. It only takes now p990 roms, but no baseband. It is working quite nicely, but is has no mobile service. How can I repartition my internal sd to be p999 again?
Peter
Szippy said:
Hello I hope someone reads this.
I have accidentally partitioned my P999 with the P990 all in one tool. It only takes now p990 roms, but no baseband. It is working quite nicely, but is has no mobile service. How can I repartition my internal sd to be p999 again?
Peter
Click to expand...
Click to collapse
Use either ROM for recovery or cleanup batch. Search development threads.
-- The noob says:
Bow your head for the android's prayer... I am an android, but I can change, if I have to, I guess
Related
http://www.multiupload.com/7FCS3EORXF
The source for the lgp506 (Aka LG Thrive), im hoping devs well get on this, and apply a p506 version for there existing roms, for them to work with the p506 correctly. Otherwise, from what i've been able to surmise is, the only issue with porting roms from the p500 to other variations seem to correlate from the kernel.
and in regard to the p506, the current cm7 rom port works, only the screen is 8-bit and showing only 3-4 pallets of blue.
Hope this source helps out.
if you dont like or cant use multiupload, other means to get the source is just going to http://www.lg.com/global/support/opensource/opensource.jsp and searching lgp506go.
its 2.2 or 2.2.x ?
ccdreadcc said:
its 2.2 or 2.2.x ?
Click to expand...
Click to collapse
i thought it was 2.2.1
Interesting
Searching the internet for phone specs.
I diff'ed the source against the P500 source.
Practically the only difference is that the P506 has two framebuffer(?) drivers (novatek and hitachi) rather than one (just hitachi), with runtime detection of hw.
Relevant kernel config is CONFIG_FB_MSM_MDDI_NOVATEK_HVGA.
Since /proc/mtd is the same for P500 and P506, I guess roms and recoveries go through with just this display glitch issue, but it'd be great to have a proper one.
Does anyone know whether it is possible to just replace the zImage in CWM/amon_ra, or a compilation is required?
I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App
Ciaox u use linux?
Any devs looking into this?
Sent from my LG-P506 using XDA Premium App
devs wont be interested, if p506 user base is very low. getting more p506 users to comment here might get devs attention ><
ccdreadcc said:
Ciaox u use linux?
Click to expand...
Click to collapse
Yes I do. Why?
BTW I love AT&T
What do you guys need? A kernel? If so get more users to coment this topic and I'll see if its reasonable to release a kernel with the extra framebuffer. But I need to be sure the user base of this phone is high enough, otherwise it's pointless.
We mostly need help with understanding the following:
Will sticking the stock P506 zImage in a cwm/amon_ra recovery, keeping the initrd and everything, just work? e.g., using mkbootimg.sh ?
The diff between P500 and P506 froyo kernels has the following changes. Are they all relevant? were some of these fixed upstream?
Novatek fb driver (and renaming of hitachi fb functions)
ami304 driver changes (support for gyro and pedometer?), including ami306 support(?) EDIT: it's the driver from Optimus V.
some minor added functionality in drivers/input/sensor/kr3dh.c
LG's fix for the touchscreen bug (?) in drivers/input/touchscreen/mcs6000_ts.c
Camera modifications (parameters, added sports scene) in /drivers/media/video/msm/isx005*
MMC changes, incl. not powering down sdcard on suspend
A change of BRCM_WLAN_SLOT to 100 instead of 2 (BCM432X related)
Units change (mul by 10) in drivers/power/msm_battery.c
USB changes in drivers/usb/gadget/msm72k*
added a call to sock_setsockopt in net/socket.c, function kernel_connect()
Would applying the diff to your kernel (or any froyo kernel) would just compile and work (assuming no conflicts)?
Would applying the diff to a gingerbread kernel work, or gingerbread has some major changes?
Is the change (at least the FB one) simple enough to convince you and/or other P500 kernel developers to incorporate it in your builds (so no fork needed)?
Thanks,
R.
+1 for interest, I've already rooted but when I looked into roms etc. for the P506 I found there weren't any so I'd be glad to test recoveries/roms
OK, I got some answers for my questions, and some new questions.
Swapping p506 zImage for p500 zImage in AmonRa 2.2.1b recovery soft-bricks. Fastboot FTW.
Swapping p506 boot.img in a stock P500h rom boots and works in full color, but the logcat is filled with an AMI304-related error.
E/AmitDaemon( 1289): [AMI304D] AMI304MID_IOCTL_GET_CONTROL error(I also get "battery hot" warnings, but maybe they're unrelated).
Not sure if accelerometer works, had to restore nandroid.
webosguru: do you have this error as well?
I think I saw that some IOCTL codes have changed in the new ami304 driver, so I guess it should be skipped in custom compilation (or fix AmitDaemon, wherever it is).
EDIT: I think this could be also fixed by using system/bin/ami304d from the AT&T rom. I wonder what other native executables I should take from stock AT&T?
I cannot find the 3 buttons required to get to recovery. Power+Home gets to fastboot, with or without VolDown. I have to use adb or rom manager.
Any ideas?
When booting a recovery via fastboot boot recovery.img, keys are not functioning. adb works, so I can flash and/or reboot recovery, but why won't they work?
I tried to grab froyo source via the repo tool, but it seems to download every piece of code ever written and then fail with some missing manifests. Ideas?
Next thing I'll do is probably to deodex and debloat the stock AT&T rom.
just happy progress, however small, is being made. Lots of smiles today.
Pursuing the deodexed stock AT&T rom path, I found out that my stock backup is (next to) worthless; it didn't include OOB info, and unyaffs fails to extract it.
I used dd if=/dev/mtdX of=/sdcard/mtdX.img instead of nandroid. I wonder if dd'ing it back and then a nandroid backup would work.
I have been following this thread. I am new to android but can help with testing out kernels.
Sent from my LG-P506 using XDA App
Really would love to see some ROM development happen for the Thrive!
Sent from my LG-P506 using XDA App
webosguru said:
I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App
Click to expand...
Click to collapse
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
And, +1 re wanting a custom kernel from P506/P505.
sd_matto said:
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
Click to expand...
Click to collapse
Install CWM for Optimus One P500 via Rom Manager.
Recovery shows weird colors, but regular rom uses a different kernel.
Now pick your favorite P500 FroYo rom, replace boot.img with your original boot.img and flash via CWM.
I still do not advise it since the ami304 daemon has problems, btw.
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
I'd like to give it a whirl anyway.
mtnlion said:
I'd like to give it a whirl anyway.
Click to expand...
Click to collapse
ONLY with safestrap, right now. If you try to flash it with the bootstrap it will softbrick your phone.
--EDIT--
Remember safestrap is not really working right now... lfaber06 and I have some highly modified versions that really are not for the rest of the world yet, and my version has a custom compiled version of CWM, and is a little buggy.
jimbridgman said:
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
Click to expand...
Click to collapse
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
lfaber06 said:
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
Click to expand...
Click to collapse
PM me a link to hashcodes d3 CM7 ported ROM (if you have one, I have had a hard time locating a completed one), and not the source code, that is what I used to compile my CM7 port with. I would like to test something, I have a theory on this, that I won't share with everyone here, since it really would not be very interesting here to anyone not trying to port these over.... we will talk more about this in PM.
Thanks!
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
JRW 28 said:
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
Click to expand...
Click to collapse
that is version 2.3.4 we are on 2.3.5 and we HAVE to use ports from 2.3.5 no way around it.
Missed that little details
CM9 does work when flash through bootstrap, I tried it the other day...
farshad525hou said:
CM9 does work when flash through bootstrap, I tried it the other day...
Click to expand...
Click to collapse
Care to share???? Plz.... it may be helpful.
Sent from my MB865 using Tapatalk
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
farshad525hou said:
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
Click to expand...
Click to collapse
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
lfaber06 said:
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yes it sure does thanks, I flashed it, played with it, and I am taking a look at a few things with your CM9 ROM, and since we PM'd I have been digging into the D3 CM7.2 version that hashcode had created. I am not quite ready to flash it yet, but maybe something tomorrow, once I have the ROM to the point that I am happy to play with it on my phone and see what works and what does not.
It looks like the issue with my old CM7 ROM, from the logs I grabbed a little while ago, with logcat, were due to kernel driver files not found during loading, so it looks like my compile had issues linking to our kernel. I so wish I had the source for our phones kernel, it would make compiling CM7 so much easier, and NO the ME865 source will not due, so don't mention it here.
Jim
Glad I could help! Also @lfaber06, what do you mean by your ported version doesn't work? That's the one I flashed.
**Edit** Also the camera doesn't work, if you guys want in to that. Probably an incorrect driver or something...
So... any news to report on either CM7 or CM9?
farshad525hou said:
So... any news to report on either CM7 or CM9?
Click to expand...
Click to collapse
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
lfaber06 said:
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
Click to expand...
Click to collapse
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
farshad525hou said:
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
Click to expand...
Click to collapse
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
lfaber06 said:
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
Click to expand...
Click to collapse
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
farshad525hou said:
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
Click to expand...
Click to collapse
That's the thing idk... I assumed that it was a Sony radio BC when I Google rlidu300-ril.so I get a device tree for a Sony. We need to know what radio we have then we can start checking sources.
Sent from my MB865 using Tapatalk
What would be involved in porting one of the Optimistic V (or other Optimistic One variants) really awesome ROMs to the LG Vortex (which is Verizion's version of the Optimums One) ?
My old Vortex is just sitting around and I wanna learn how to make ROMs. It can't be too hard to get a ROM working on it, the only difference is the radio, as far as I can tell, and that would be just replace some files, right?
So I'm hoping someone who knows a lil more than me can tell me what I need to change to make a ported ROM off someone's Optimistic One variant source.
ANYONE? not a hard question....
Not a hard question??? What do YOU think is involved. porting to a completely new phone AOSP or whatever is way harder than you think. You need to compile from source to get a fully working rom. I cannot do this but you should try first messing around. You don't even have CWM on the Vortex, so you should go and ask that first...
Sent from my LG-P500 using Tapatalk
You can port different kinds of Rom to your phone which are cdma-based.
If you use your stock kernel roms should boot (can't say anything about data/wifi/gsm)
If you want to build your own, look here for a base.
And don't forget to backup your rom! It has different libs you may need to use!
You can find CWM for your phone here!
You'll also find a CM7 for your phone to play with
Good luck!
Rores said:
Not a hard question??? What do YOU think is involved. porting to a completely new phone AOSP or whatever is way harder than you think. You need to compile from source to get a fully working rom. I cannot do this but you should try first messing around. You don't even have CWM on the Vortex, so you should go and ask that first...
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Actually, there is a custom recovery. And the hardware is identical to other optimus one variants, except for the radios. So there should be files that correspond to ththe radios that need to be replaced. Now I've never built a ROM before, just tinkered with one, but I don't expect it to be THAT hard to swap out a few files, maybe recompile the kernel.
_Arjen_ said:
You can port different kinds of Rom to your phone which are cdma-based.
If you use your stock kernel roms should boot (can't say anything about data/wifi/gsm)
If you want to build your own, look here for a base.
And don't forget to backup your rom! It has different libs you may need to use!
You can find CWM for your phone here!
You'll also find a CM7 for your phone to play with
Good luck!
Click to expand...
Click to collapse
There are several other CDMA Optimus One variants, I know they're available for sprint and virgin at least. If I keep the stock Verizon kernel how I change a sprint/virgin ROM to be compatible?
Its very easy, just go into the build.prop and change everything that calls for vm670 and change it to vs660 and do the same in the updater script. You'll be able to flash it and use it, but data, calling and sms wont work , you need to swap the telephony files from the same android version, I'm currently porting JB to the vortex
jacobmacek said:
Its very easy, just go into the build.prop and change everything that calls for vm670 and change it to vs660 and do the same in the updater script. You'll be able to flash it and use it, but data, calling and sms wont work , you need to swap the telephony files from the same android version, I'm currently porting JB to the vortex
Click to expand...
Click to collapse
Attempting to port this rom to the LG Vortex. Any advice?
Hi all, thanks for taking the time to read.
I have a LG G2X, love the feel, the display, the specs and the price. Hate the phone....in every other way
I am on my 4th G2X now b/c I keep taking it back to T-Mobile to get a new one based on the following things my phone does:
1. It restarts 1-2x a week, randomly with or without a power adapter plugged
2. It freezes up every other day or so and requires a hard restart (battery pull) to resume use
3. It frequently takes 5+ minutes to get a GPS lock (tried in several cities coast to coast US)
Now if it were just the first phone I could say lemon, but every G2X I have owned does this, T-Mobile told me it was a known issue with the phone but couldn't tell me if it was software or hardware in nature.
So my question to you fellow forumites is this: Is the issue hardware related (move on to another phone) or software (Rom install fixes all my worries and I'm happy forever and ever and ever)?
If you're still using the stock ROM, and are still on 2.3.3, then you are experiencing SW suckage... Get a custom CM7 Rom on there and enjoy some of the finer benefits. Stability will be better but you won't be dead-set stable. GPS has been an issue for some since the inception of the phone. Others have GREAT GPS reception.
Research the Development forums and find a CM7.2 ROM that best suits you. You can of course go CM9 (ICS) but you won't get HW Acceleration and some things just flat out don't work yet.
New2my8125 said:
If you're still using the stock ROM, and are still on 2.3.3, then you are experiencing SW suckage... Get a custom CM7 Rom on there
Click to expand...
Click to collapse
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
mog44net said:
Hi all, thanks for taking the time to read.
I have a LG G2X, love the feel, the display, the specs and the price. Hate the phone....in every other way
I am on my 4th G2X now b/c I keep taking it back to T-Mobile to get a new one based on the following things my phone does:
1. It restarts 1-2x a week, randomly with or without a power adapter plugged
2. It freezes up every other day or so and requires a hard restart (battery pull) to resume use
3. It frequently takes 5+ minutes to get a GPS lock (tried in several cities coast to coast US)
Now if it were just the first phone I could say lemon, but every G2X I have owned does this, T-Mobile told me it was a known issue with the phone but couldn't tell me if it was software or hardware in nature.
So my question to you fellow forumites is this: Is the issue hardware related (move on to another phone) or software (Rom install fixes all my worries and I'm happy forever and ever and ever)?
Click to expand...
Click to collapse
Software...........I am running Hellfire Phoenix ROM and flashed a GPS fix, and new baseband, now I get GPS locks within <>10 seconds, my phone never freezes, or reboots.
wmm said:
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
Click to expand...
Click to collapse
+1
Sent from my LG-P999 using xda premium
wmm said:
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
Click to expand...
Click to collapse
Thanks for the great responses guys, just another reason I love this forum.
I should have given a few more details, I am running stock 2.3.3 on T-Mobile in the US.
Few questions for a techie (but virgin ROMer):
1. Is the 2.3.4 stock available OTA? I haven't seen any available upgrades.
2. What does baseband refer to? (trying to educate myself on the terms)
3. Any favorite ROMs? My must haves are stability and speed, other than that any goodies/awesomeness is welcome but the first two are absolute.
I am tempted to stick to stock ROMs as I haven't flashed one myself yet and this phone is my lifeblood b/c of work.
On a scale of 1-10 where 1 is "I did it with on accident when I dropped it down the stairs" and 10 is "the most difficult thing you will ever do in your life" what is the difficulty for a ROM virgin to sucessfully flash to 2.3.4 (if it is not available OTA) or CM7/other ROMs,etc?
I am technical, 12 year IT professional with MCSA/CCNA, etc but haven't done much research into the ROM biz. If its not too difficult is there a "Must read" guide for noobs?
mog44net said:
Thanks for the great responses guys, just another reason I love this forum.
I should have given a few more details, I am running stock 2.3.3 on T-Mobile in the US.
Few questions for a techie (but virgin ROMer):
1. Is the 2.3.4 stock available OTA? I haven't seen any available upgrades.
2. What does baseband refer to? (trying to educate myself on the terms)
3. Any favorite ROMs? My must haves are stability and speed, other than that any goodies/awesomeness is welcome but the first two are absolute.
I am tempted to stick to stock ROMs as I haven't flashed one myself yet and this phone is my lifeblood b/c of work.
On a scale of 1-10 where 1 is "I did it with on accident when I dropped it down the stairs" and 10 is "the most difficult thing you will ever do in your life" what is the difficulty for a ROM virgin to sucessfully flash to 2.3.4 (if it is not available OTA) or CM7/other ROMs,etc?
I am technical, 12 year IT professional with MCSA/CCNA, etc but haven't done much research into the ROM biz. If its not too difficult is there a "Must read" guide for noobs?
Click to expand...
Click to collapse
Difficulty is pretty low. If you can follow instructions, and understand what you're doing, then you should be good to go. If you want 2.3.4, you're gonna need to use LG's ****ty software. Either you use KDZ flasher, or LG's official PC suite. Both crashed on me constantly on Win7 x64. I was lucky/unlucky, it crashed right after writing the baseband (low level radio firmware). It hadn't even partitioned anything yet if I tried to turn it on, not even a backlight was showing. So I had to use NVflash to completely repartition it to stock. After that, I flashed CWM (clockworkmod), the custom recovery. Nowadays, TWRP is available. TWRP is awesome, and they have awesome Devs. TWRP (teamwin recovery project) is touch based rather than CWM and traditional volume key and power button navigation. There is CWM touch, but it's extremely experimental and I find it too glitchy compared to TWRP. TWRP is a work in progress however and there may be issues (I had one but it was easily fixed with one command when I spoke with the Devs on irc) I haven't had any serious ones though. IMO it's easier to NVflash in a Linux environment, because there is no messing around with drivers. But after drivers are installed on windows, the difficulty level plateaus.
As for my favorite ROM, that would currently temasek cm7 builds. They're stable, fast and they're customizable as f***.
I don't have any links right now, because I'm on my phone, (I can grab them later/soonish) you're going to want tga_gunman's thread named something along the lines of "One click recovery flasher" that's for CWM recovery. If you want TWRP, there's a thread that has TWRP in the title.
Also look for "ROM for recovery under NVflash" or something similar to that. That will take you back to complete stock 2.3.3 no matter what happened software wise, unless you somehow managed to break the baseband. The baseband is the only thing that cannot be fixed by NVflash, only can be fixed by LG's ****ty PC software.
For temasek's cm7 builds, the thread is not created by temasek, but the builds are by him. It should be at build 133 or 134.
If you need anything else, PM me maybe.
Good deal, I'm planning on following this thread from the general section (http://forum.xda-developers.com/showthread.php?t=1594650).
I'm leaving out of state but will work on it over the weekend.
Thanks for all your help and support everybody, any additional comments are welcome before I start flashing this weekend.
Q - Do I need to get the owain's baseband flash fix or not with the ROM you sugested, the comments on the thread are confusing me a bit. If so where can I download the correct one, can't seem to find it in the Dev threads.
mog44net said:
Good deal, I'm planning on following this thread from the general section (http://forum.xda-developers.com/showthread.php?t=1594650).
I'm leaving out of state but will work on it over the weekend.
Thanks for all your help and support everybody, any additional comments are welcome before I start flashing this weekend.
Q - Do I need to get the owain's baseband flash fix or not with the ROM you sugested, the comments on the thread are confusing me a bit. If so where can I download the correct one, can't seem to find it in the Dev threads.
Click to expand...
Click to collapse
You only need that baseband fix if you have the latest baseband (March 2012) from v21y. It should be available in owain's hopto.
tahahawa said:
You only need that baseband fix if you have the latest baseband (March 2012) from v21y. It should be available in owain's hopto.
Click to expand...
Click to collapse
Help a noobie out, what/where is owain's hopto?
Edit: I'll test without the fix, to be sure and flash the baseband if needed, i understood from the comments in the ROM's thread that its needed for Bluetooth calls.
I might have found the baseband fix link (http://forum.xda-developers.com/showthread.php?t=1776843) can anyone confirm?
mog44net said:
Help a noobie out, what/where is owain's hopto?
Edit: I'll test without the fix, to be sure and flash the baseband if needed, i understood from the comments in the ROM's thread that its needed for Bluetooth calls.
I might have found the baseband fix link (http://forum.xda-developers.com/showthread.php?t=1776843) can anyone confirm?
Click to expand...
Click to collapse
That's the one
Edit: if you need Bluetooth calling on the new baseband, don't flash any cm ROMs. Stay on the old one if you need/want Bluetooth calling.
tahahawa said:
That's the one
Edit: if you need Bluetooth calling on the new baseband, don't flash any cm ROMs. Stay on the old one if you need/want Bluetooth calling.
Click to expand...
Click to collapse
Firstly thanks for all the good Q/A, like a good forum noobie, I'm marking thanks each reply.
I want to make sure I understand your comment. This is what I understood, let me know if I'm off/on. The CM Roms do not work with BT calling, so I should stick with stock if that's important to me? I would assume then for me to get beyond my current issues (OP) my best bet would be to Flash the 2.3.4 stock?
Thanks again for the info and time.
***edit***
Nix the above. I completely read it wrong, thought you were saying all CM ROMs didn't work with Bluetooth. Just so on the current Baseband.
I'm on Jul 15 2011 Baseband currently, so I'll attempt the CM7 ROM this weekend when I'm back home and able to devote more focus. Coming from stock 2.3.3 do I need to flash a kernel as well or will that be in the ROM <---showing my ROM noobness but unashamed to learn.
mog44net said:
Firstly thanks for all the good Q/A, like a good forum noobie, I'm marking thanks each reply.
I want to make sure I understand your comment. This is what I understood, let me know if I'm off/on. The CM Roms do not work with BT calling, so I should stick with stock if that's important to me? I would assume then for me to get beyond my current issues (OP) my best bet would be to Flash the 2.3.4 stock?
Thanks again for the info and time.
Click to expand...
Click to collapse
If you decide to get the newer baseband (you get it with 2.3.4 kdz, only way to get new baseband) and bt calling is important, do not go to cm. If you don't mind staying on the older baseband, bt calling will work fine on cm.
tahahawa said:
If you decide to get the newer baseband (you get it with 2.3.4 kdz, only way to get new baseband) and bt calling is important, do not go to cm. If you don't mind staying on the older baseband, bt calling will work fine on cm.
Click to expand...
Click to collapse
Lol, I feel so dumb, its like learning a new language while being held underwater.
kdz=?
I'm trying to understand why I would decide to get the newer baseband? If I do I can use BT calling but can't use CM7 ROMs, if I don't I can use CM7 ROMs and BT calls should work fine. Dont see the upside to upgrading the baseband, unless it has issues?
BTW as I haven't seen it, I get happy feelings when I look at your avatar
mog44net said:
Lol, I feel so dumb, its like learning a new language while being held underwater.
kdz=?
I'm trying to understand why I would decide to get the newer baseband? If I do I can use BT calling but can't use CM7 ROMs, if I don't I can use CM7 ROMs and BT calls should work fine. Dont see the upside to upgrading the baseband, unless it has issues?
Click to expand...
Click to collapse
KDZ = LG's proprietary file type to update their phones via PC officially. A lot of people say the new baseband gives them better gps and call quality. Basically if you don't change baseband to the new one, everything will work perfectly. If you DO switch, everything will work perfectly, but only on stock. Everything will work on cm except Bluetooth calling with the new baseband. I don't think it's worth restricting yourself to stock because of the new baseband and and bt calling. My recommendation? Don't change baseband, just go to cm. Also, soon we might start to see android 4.1.1 jelly bean. They won't be stable for a while though.
Too much fun.
Couldn't wait, just finished flashing CWM, then backed up, then wiped like 400x then dropped the CM7 ROM you sugested.
Longest 10 minutes of my life letting it sit.
Working great, I'll update here with any additional info or create a new thread.
TY TY TY all
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
mog44net said:
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
Click to expand...
Click to collapse
If it's cm7 get the latest gb one, if it's cm9 get the latest ics one... It has gb or ics in the name of the file.
Sent from my LG-P999 using xda app-developers app
cainG2x said:
If it's cm7 get the latest gb one, if it's cm9 get the latest ics one... It has gb or ics in the name of the file.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Much thanks, i'll do that now.
Any ideas on being stuck on EDGE network only?
mog44net said:
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
Click to expand...
Click to collapse
Yeah goo.im/gapps is the best. For the cell network, try going settings> wireless>mobile>network operators and select "select automatically"
Okay this question has been bugging me for a while now. Everyone is waiting on RC aka Ricardo AKA..... on getting the ported p990 to then be ported over to p999. We have many fine Developers here like Eagleblood , Rafase282, tonyp, Kashamalaga and many MIA ones that may or may not return like nycelitemaster, owain94, x0xhellx0x and my favorite Mr. Apocalypse.
My question is simple and would love one of these guys to answer it if possible.
Why are we waiting for RC to port it over when anyone of you guy have done it before. Am I wrong when saying that most of you have ported P990 over to P999 before? I respect everyone I have named. You have brought new life to my G2X. JUst wondering why we wait for RC, like he is the only one who can do this. Please if I am missing something let me know. thanks
I believe they are waiting for a more stable release of CM10 for the P990 before they bother to port it over for the P999. They should have many of the same bugs that need to be worked out. There is no need to do it twice.
I felt the same thing. Can some of the Developers list above or others I missed confirm this? Maybe this can stop or slow down the rants. The only reason I feel it may not be a difficult thing to do it because of this guys post...
Lezo OS
Hello everyone.
This is a port of the P990 Lezo OS a CM based rom. I am not a developer, just someone who was lucky enough to have this work It's just another piece of a so called "Crack Flashing Series". There are plenty of roms provided to our community, and this also brings people with different likes and dislikes. I aim only to share some of the other roms out there with the community. Maybe you want to try something out inbetween updates from your favorite rom, well, try this.
None of this would out be possible without the help of guides from dubntz and blindndumb. If you like any of the ports thank them as well.
This guy has done it before with other p990 Roms with little experience.
When we were on Cm7 we were able to port roms by using the already created cm7 base. The problem now is we don't even have a P999 cm10 base to port with, which is why we're waiting on RC since he needs to create the base.
Sent from my Nexus 7 using xda app-developers app
That seems to make sense. thanks. Can any Developers confirm this. Is RC truely the only one? Or is he just the only one with the spare time to help us? thanks
We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI
nycelitemaster said:
We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI
Click to expand...
Click to collapse
Don't we already have the drivers and Kernal? They are part of p990 and then don't they just need to port it over.
More then likely it would be easier to port tonyps experimental ics. We can compile a kernel for it and have the drivers. We just need the experience lol
Sent from my LG-P999 using Tapatalk
Here's what I think based off what I have read:
I think first and foremost, our Dev's who all own P990's are working in wrapping their wits around the sources for their phones, us and our G2x's are the red-headed step-children (figuratively) of LG. The phone has potential, but gets little attention. I also believe that the Devs are waiting for a kernel to be built with the new sources, which those sources have to be altered to work with the G2x, as they did for the O2x. Something which I don't think our Devs want to do. I may be wrong, but I would think that Bene, or Dj V. have the know-how to do it. Again, we're back to the fact that they're (understandably) going to do work for their phones first.
Sent from my LG-P999 using xda premium
As far as I know, the kernel sources for su660 has some issues compiling kernel for p999. It can be one of the reason why we don't have cm10 yet. I believe the developers are working on it. Also the kernel source comes with locked boot loader. So its essential to port old boot loader which is not locked to the new kernel. This might also be preventing other developers from building kernel. If I have time, I will try to see if I can compile the kernel with old boot loader or not this weekend. I am a full time science student. I think to port the p990 ROM we just need a p999 kernel and some p999 specific drivers such as ril drivers. I do hope the cm10 comes asap though. I might be wrong.
While I do not consider myself a developer, I thank you for listing me there. I personally do not have the time and knowledge required to build a cm10 base for the p999 based off the p990. The kernel and rom needs to be change to work for our phones. Also as it was said already, it would make no sense to make an early port, based on RC work which will most likely piss him off if we start kanging and using his work while it is not even stable enough to build for our phone. So I would say that out of respect and time/knowledge required most people able to make the port would either wait for help debugging the p990 version so it can be ported to other devices without the same issues to be fixed twice or more times.
In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app
guitarist5122 said:
In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.
who wants a kernel?
I've posted a kernel built from the cm10 lge-kernel-star repo in the dev thread, maybe somebody feels like taking it for a spin.
was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.
rosevilletoyota said:
was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.
Click to expand...
Click to collapse
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium
Rafase282 said:
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.
Click to expand...
Click to collapse
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)
bakedpatato said:
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)
Click to expand...
Click to collapse
For my name the division is Rafa-sé It is just that in many places I cant use the é. SO I left it as an e and use use é for the phonetic part.
Morphine! :highfive:
Волк said:
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Is the lge_star_ril something LG was supposed to have included? From my (limited) kernel knowledge, that bit seems pretty vital to having a properly working phone.
Without it, how hard is it going to be to get working calls/data/gps without having serious battery and quality issues as you've alluded to?
It was missing from the old sources, and yea, like I said alot of the deal-breaking issues were due to that, the ICS (which I think was already hacked) was hacked into JB.
Sent from my LG-P999 using xda premium