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.
Related
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?
Alpha release of CM7.2 for Micromax A70.
Ported using dsixda kitchen's porting tools (from a LG P500 ROM based on CM7.2 nightly).
Micromax A70 basic info:
Runs on Froyo 2.2.1 presently.
Kernel: 2.6.32.9-perf
600MHz processor.
MSM7627.
256Mb RAM + 160Mb ROM.
Adreno 200 GPU.
Things that work:
Hardware keys.
Sound.
Things that don't:
Touch.
Cellular.
No ADB => No logcat.
Nothing else works apart from that mentioned as working.
No kernel source provided my Micromax even after many requests from many people.
Requesting help from xda devs to help with this.
Regards
DOWNLOAD
Need to flash this afterwards: Boot
How to flash:
1.) Flash the ROM using recovery. (Worked for me both with and without clearing data or cache)
2.) Flash the attached "boot.img flasher.zip"
P.S. Although the boot.img flasher and the rom have save boot.img, it won't boot unless you flash the boot.img flasher zip.
for keys are you changed keychars and keylayout folder under in usr folder with any a70 rom. If not change now so key will work
cips gokhle said:
for keys are you changed keychars and keylayout folder under in usr folder with any a70 rom. If not change now so key will work
Click to expand...
Click to collapse
Hardware keys work as they are supposed to.
Which means the keychars and all are correct.
The touch based keys don't work (as touch doesn't work).
main thing
you are ported cm7.2 nightly rom. Which is nbb(new baseband) for nbb need .35 kernel a70 have .35 kernel. .35 kernel need to fix many bugs . If a70 have .35 then this bug will be fix but don' have then it will very very hard to fix gsm and other bugs. If a70 have .32 kernel then then try to port mike os cm7 rom. It's obb(old baseband) it will work with a70. Nbb to obb port is hard. You can port nbb rom to obb only in this device. If you port nbb rom from other device and don't have any .35 kernel then it hard to fix. And best luck for your rom
cips gokhle said:
you are ported cm7.2 nightly rom. Which is nbb(new baseband) for nbb need .35 kernel a70 have .35 kernel. .35 kernel need to fix many bugs . If a70 have .35 then this bug will be fix but don' have then it will very very hard to fix gsm and other bugs. If a70 have .32 kernel then then try to port mike os cm7 rom. It's obb(old baseband) it will work with a70. Nbb to obb port is hard. You can port nbb rom to obb only in this device. If you port nbb rom from other device and don't have any .35 kernel then it hard to fix. And best luck for your rom
Click to expand...
Click to collapse
Thanx for that info
But the problem is, whatever ROM is tried to port...touch never works
Tried with AOSP GB and even CM6 didn't work
akshaybz said:
Thanx for that info
But the problem is, whatever ROM is tried to port...touch never works
Tried with AOSP GB and even CM6 didn't work
Click to expand...
Click to collapse
can you expalin full toch problem. I mean are you see any ring in screen or full toch is not working?
cips gokhle said:
can you expalin full toch problem. I mean are you see any ring in screen or full toch is not working?
Click to expand...
Click to collapse
Full touch ain't working.
Additional info:
A dev, PlayfulGod, created a boot.img from CM source (changed the ramdisk), using that we were able to boot into these ported ROMs.
If we use stock boot.img, we just have black screen or bootloops.
I flashed that boot.img over stock ROM, touch worked then.
Which means the problem ain't from the kernel.
akshaybz said:
Full touch ain't working.
Additional info:
A dev, PlayfulGod, created a boot.img from CM source (changed the ramdisk), using that we were able to boot into these ported ROMs.
If we use stock boot.img, we just have black screen or bootloops.
I flashed that boot.img over stock ROM, touch worked then.
Which means the problem ain't from the kernel.
Click to expand...
Click to collapse
let me see if I can fix that while compiling from source.
Are you able to separate/find out the touchscreen drivers from stock?
akshaybz said:
Full touch ain't working.
Additional info:
A dev, PlayfulGod, created a boot.img from CM source (changed the ramdisk), using that we were able to boot into these ported ROMs.
If we use stock boot.img, we just have black screen or bootloops.
I flashed that boot.img over stock ROM, touch worked then.
Which means the problem ain't from the kernel.
Click to expand...
Click to collapse
that mean a70 have custom kernel. And you used stock kernel to port rom? Also some time needed to add full toch driver in kernel. But it's not always need. And i don't know more info in a70. Are you asked help from playfullgod? First time i see toch problem in gb. Ics have toch problem. I think other a70 dev will help you to fix toch. Because i never used a70. If you faced ring problem then i can help. In other ported rom adb was working if working then you will find why toch is not working. And in cm7 roms always use custom kernel.
abhis3k said:
let me see if I can fix that while compiling from source.
Are you able to separate/find out the touchscreen drivers from stock?
Click to expand...
Click to collapse
Nope.
cips gokhle said:
that mean a70 have custom kernel. And you used stock kernel to port rom? Also some time needed to add full toch driver in kernel. But it's not always need. And i don't know more info in a70. Are you asked help from playfullgod? First time i see toch problem in gb. Ics have toch problem. I think other a70 dev will help you to fix toch. Because i never used a70. If you faced ring problem then i can help. In other ported rom adb was working if working then you will find why toch is not working. And in cm7 roms always use custom kernel.
Click to expand...
Click to collapse
A70 doesn't have kernel source.
Can't use custom kernel.
We can only modify the ramdisk.
PlayfulGod doesn't have A70 either....
akshaybz said:
Nope.
A70 doesn't have kernel source.
Can't use custom kernel.
We can only modify the ramdisk.
PlayfulGod doesn't have A70 either....
Click to expand...
Click to collapse
Let me make this clear : A ramdisk is something which helps you to boot. After booting drivers are provided by kernel. No wonder, the touch works in stock.
And yes, Micromax has a custom kernel. They have confirmed this over mail. This is the sole reason they did not provide the kernel source code.
I have seen the stock rom thoroughly. The touchscreen firmware there is a binary ts_fw.i. We have to use that one along with yamato firmwares if we need the radio to work in CM7.2. Let me finish downloading the sources. I am ATM building the vendor & device folders & will upload to github when finished.
P.S. I own a LG-P500 myself and I can tell you even if they use same Qualcomm MSM7227 Chipset, form factor is different in both. A70 uses msm7x27_surf form factor.
---------- Post added at 01:06 AM ---------- Previous post was at 12:52 AM ----------
Code:
[B][I]/system/etc/firmware
|-- ts_fw.i
|-- wlan
| |-- cfg.dat
| |-- qcom_cfg.ini
| |-- qcom_fw.bin
| `-- qcom_nv.bin
|-- yamato_pfp.fw
`-- yamato_pm4.fw[/I][/B]
This is the current firmware tree. You need ts_fw.i for touchscreen to work.
abhis3k said:
Let me make this clear : A ramdisk is something which helps you to boot. After booting drivers are provided by kernel. No wonder, the touch works in stock.
And yes, Micromax has a custom kernel. They have confirmed this over mail. This is the sole reason they did not provide the kernel source code.
I have seen the stock rom thoroughly. The touchscreen firmware there is a binary ts_fw.i. We have to use that one along with yamato firmwares if we need the radio to work in CM7.2. Let me finish downloading the sources. I am ATM building the vendor & device folders & will upload to github when finished.
P.S. I own a LG-P500 myself and I can tell you even if they use same Qualcomm MSM7227 Chipset, form factor is different in both. A70 uses msm7x27_surf form factor.
Click to expand...
Click to collapse
Can you tell me what exact email they sent?
Tried adding those firmware files, booted but touch didn't work.
akshaybz said:
Can you tell me what exact email they sent?
Tried adding those firmware files, booted but touch didn't work.
Click to expand...
Click to collapse
Dear Valued Customer,
Thank you for your Email, we would like to inform you that the kernel source key cannot be provided.
For any further Assistance and Query you can contact us on the Customer Support & number given below:
18605008286
You can also log onto our website for information www.micromaxinfo.com
Thanks & Regards, MMX SUPPORT
This was the exact details.
Sent from my LG-P500 using XDA
abhis3k said:
Dear Valued Customer,
Thank you for your Email, we would like to inform you that the kernel source key cannot be provided.
For any further Assistance and Query you can contact us on the Customer Support & number given below:
18605008286
You can also log onto our website for information www.micromaxinfo.com
Thanks & Regards, MMX SUPPORT
This was the exact details.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
I was taking about the point when you said that they confirmed over mail that they have custom kernel...
Let it be
Did you download the ROM and tried anything?
If we connect device to PC, device only shows charging....
No hint of a USB being connected.
Unless they have custom kernel there is no point hiding the kernel source.
BTW firmware won't load if it is tied to specific kernel version or it is requested by the driver via system call.
No I haven't tried the rom. Can't download it unless sync finishes.
Sent from my LG-P500 using XDA
get stock rom and then try porting.
Copy boot.img of stock rom and extract it you will get everything you want.
karandeepdps said:
get stock rom and then try porting.
Click to expand...
Click to collapse
That's what I used.
karandeepdps said:
Copy boot.img of stock rom and extract it you will get everything you want.
Click to expand...
Click to collapse
What am I supposed to get?
I know the difference b/w the stock boot.img and this one.
Please be more clear on this one
I downloaded n flashed the rom but it didn't go past bootlogo(mmx logo)..i had to pull battery,tried again,no luck..went back for stock then flashed again but same.do i need some specific steps to take..n before some1 ask,i waited at bootlogo for abt 15-20 mins..
mastermind1024 said:
I downloaded n flashed the rom but it didn't go past bootlogo(mmx logo)..i had to pull battery,tried again,no luck..went back for stock then flashed again but same.do i need some specific steps to take..n before some1 ask,i waited at bootlogo for abt 15-20 mins..
Click to expand...
Click to collapse
After flashing the ROM, you have to flash the attached boot.img afterwards ...
Dunno why..
Although the boot.img is same as in ROM but it only boots if you flash it again :/
Let's try get cm10 too boot atleast im downloading the sources i read a few guides every omap4 device except the lg optimus 3d is either running cm9 or cm10 im gonna try to get it to atleast boot even if nothing else work right well something todo till lg decides to do the upgrade. by the way in the GB Sources for the lg p940 in the kernel sources it contains stuff to do with our phone driver wise i think the only thing that differs is camera + ram.
anybody tried it before?
I'm thinking of trying it, please link the guides you've found!
Sent from my LG-P920 using xda app-developers app
Good luck guys we are all "rooting" (hahah get it, get it ) for you guys , defcomg are you going to try and port the prada ics first and then cm10, or directly ??
If you're hell bent on trying, I would suggest porting a mixture of the Prada ICS and CM10: Prada ICS for most of the drivers and code to make things work and CM10 for the base. This is because you have the CM10 source so it's easy to modify what doesn't work, since the Prada ICS kernel probably won't work out of the box anyway. You could port Prada ICS wholesale but I suspect more things won't work that way given CyanogenMod often has open source blobs for most of the drivers and for whatever chips that are different from the Prada phone whose drivers you need.
defcomg said:
anybody tried it before?
Click to expand...
Click to collapse
yes, but i got an non booting ramdisk + a zipp without media, fonts, vendor and apps.
but it could also be that i have failed, today i will tray it again so let's hope somebody will make it
FPtje said:
I'm thinking of trying it, please link the guides you've found!
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
http://www.kernel-xp.net/index.php/en/guide/25-android/32-compilare-cm10
http://wiki.cyanogenmod.com/wiki/Building_from_source
http://forum.xda-developers.com/showthread.php?t=1668483&highlight=build+cm9+source
http://forum.xda-developers.com/showthread.php?t=1668396
http://forum.xda-developers.com/showthread.php?t=1807505&highlight=build+cm10
rezzsha said:
Good luck guys we are all "rooting" (hahah get it, get it ) for you guys , defcomg are you going to try and port the prada ics first and then cm10, or directly ??
Click to expand...
Click to collapse
Was gonna port it directly i was gonna run a comparison on winhex to see how the kernels differ
pandaball said:
If you're hell bent on trying, I would suggest porting a mixture of the Prada ICS and CM10: Prada ICS for most of the drivers and code to make things work and CM10 for the base. This is because you have the CM10 source so it's easy to modify what doesn't work, since the Prada ICS kernel probably won't work out of the box anyway. You could port Prada ICS wholesale but I suspect more things won't work that way given CyanogenMod often has open source blobs for most of the drivers and for whatever chips that are different from the Prada phone whose drivers you need.
Click to expand...
Click to collapse
Repo failed have to start over damn i think i have identified a few chips. if there was a way to get the kernel what drivers are loaded
Well that's new. Did you do repo init, repo sync and also installing all the dev tools as recommended here (http://source.android.com/source/initializing.html)? To extract the drivers, you'll have to decompile the Prada ICS kernel, extract the drivers, find a CM10 supported device with similar hardware, replace drivers for the different hardware, do a bit of coding to set up a new CM branch on your com and set up brunch/lunch and vendorsetup/makefile and fill it up with the files mentioned above and see if you can compile it.
http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide
Hope this helps! Good luck!
Sent from my phone.
good luck and hope you manage this would be amazing. A big thank you just for your effort
I just started a new cm9 build with prada ics kernel but with my lame pc it will take some time.
pandaball said:
Well that's new. Did you do repo init, repo sync and also installing all the dev tools as recommended here (http://source.android.com/source/initializing.html)? To extract the drivers, you'll have to decompile the Prada ICS kernel, extract the drivers, find a CM10 supported device with similar hardware, replace drivers for the different hardware, do a bit of coding to set up a new CM branch on your com and set up brunch/lunch and vendorsetup/makefile and fill it up with the files mentioned above and see if you can compile it.
Click to expand...
Click to collapse
Closest Device Running CM10 Same SOC
[JB]Samsung I9100G - https://github.com/CyanogenMod/android_device_samsung_i9100g/tree/jellybean
[ICS]LGE P940 - https://github.com/milaq/android_device_lge_p940
Would This Work Replace the LIBS and Configs in devices/samsung/i9100g with the ones from Prada Compile then in the OUT Folder replace WIFI MOdule wpa_sup the issue here is the kernel i can modify the ICS Kernel of the Prada to Match that of the p920 most things are the same its only a few files that change when kernel is compiled should i just place it on the root of the device folder?
I din't know if that stuff that I think make sense but wouldn't it be better if we try to make at first
a working cm9 zip, and after that try to port cm10? It's because there are already some tutorials of how
to "converting" ics into jellybean.
I also started again building a cm9 build, this time with ics prada kernel source and
the command
Code:
make otapackage
instead of brunch p920.
But it will take some time to compile that because my PC isn't the best (single core 2.8 ghz Intel celeron with 2gb RAM)
This looks way too difficult for me. While I might be able to build Android, I'll have no clue on how to debug or fix issues.
berni987654321 said:
I din't know if that stuff that I think make sense but wouldn't it be better if we try to make at first
a working cm9 zip, and after that try to port cm10? It's because there are already some tutorials of how
to "converting" ics into jellybean.
I also started again building a cm9 build, this time with ics prada kernel source and
the command
Code:
make otapackage
instead of brunch p920.
But it will take some time to compile that because my PC isn't the best (single core 2.8 ghz Intel celeron with 2gb RAM)
Click to expand...
Click to collapse
Well Im Runnning UBUNTU on VMware left it compiling a test build i have two Sources JB/CM @ Android/system ICS/ASOP @ Working_Directory. i just thought it would be much easier to just complile cm10 instead of cm9 then cm10 let me know how your build goes. The Prada Kernel is it modded for P920 or is it stock.
Most tutorials to Compile from Source are not good maybe we could ask codeworx for help he got JB Running on the i9100g
The Needs to be a Convert CM7 to CM9 to CM10 Guide.
FPtje said:
This looks way too difficult for me. While I might be able to build Android, I'll have no clue on how to debug or fix issues.
Click to expand...
Click to collapse
i know what you mean before attempting this i had not even used linux but guides and tuts can only get you so far when Ricardo had a working cm9 all that was whacked was the dsp this was before the lg prada it now has ics wonder why he did not get required dsp drivers and modules from prada ics source it would be cool if he released CM9 at whatever state its in im sure we would manage to get it fully functional
defcomg said:
i know what you mean before attempting this i had not even used linux but guides and tuts can only get you so far when Ricardo had a working cm9 all that was whacked was the dsp this was before the lg prada it now has ics wonder why he did not get required dsp drivers and modules from prada ics source it would be cool if he released CM9 at whatever state its in im sure we would manage to get it fully functional
Click to expand...
Click to collapse
Well I dont thinks so that's gonna happend, I just asked him that on G+ and he said "No".
this time i managed to get apps but who finds the fail?
berni987654321 said:
this time i managed to get apps but who finds the fail?
Click to expand...
Click to collapse
Fail? is it the apps only are the other folder libs etc bin also compiled?
My build was taking to long so i stopped it will attempt again in the weekend this Source Compilation is way hectic
I meant that there's a nfc.apk in the app folder xD . My computer is now working since 9 hours.
app, etc, framework, fonts should be ready but there are some libs missing and I don't know about
the other folders so let's hope that I'm getting this atleast to the cm9 bootanimation.
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
my terminal is completly full just with compiling libwebcore -_-'
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
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