p760 to p769 porting - LG Optimus L9 P760, P765, P768, P769

someone needs to make a guide because i can boot p760 roms but screen is reversed and with different kernel's i get instant reboot on lg logo.

---

thasilenthacker said:
someone needs to make a guide because i can boot p760 roms but screen is reversed and with different kernel's i get instant reboot on lg logo.
Click to expand...
Click to collapse
The easiest way is
1. Replace kernel with working P769 kernel.
2. Replace all propeitrary files with P769 version. (You can have these files list from CM)
3. Add some more libraries (I don't know which files. I got brightness config doesn't working problem but I cannot solve it.)
I think that's all. Then you can add some customize to the rom. I used to port MIUI to P769 and that is what I did. But you may have some problem with some hardware library which is not in propreitary files list. It's an trial and error process but you need to have P769 to test it.

---

@artit do you think you could list the exact files please?

---

I was trying to figure out how to get jellybean on p769 but I haven't figured it out lol. I tried building from aosp and got some error I couldn't figure out. I was trying to build aosp, and using Anton X sources.
Sent from my Nexus 4 using Tapatalk

---

thasilenthacker said:
@artit do you think you could list the exact files please?
Click to expand...
Click to collapse
You better use AntonX repo https://github.com/AntonX/android_vendor_lge_p769
Juanito216 said:
I was trying to figure out how to get jellybean on p769 but I haven't figured it out lol. I tried building from aosp and got some error I couldn't figure out. I was trying to build aosp, and using Anton X sources.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I also tried to build AOSP but cannot boot it up. We already have L9 device tree, it's easier to build CM, AOKP, PAC or AOSPA than AOSP.

---

artit said:
You better use AntonX repo https://github.com/AntonX/android_vendor_lge_p769
I also tried to build AOSP but cannot boot it up. We already have L9 device tree, it's easier to build CM, AOKP, PAC or AOSPA than AOSP.
Click to expand...
Click to collapse
I attempted before CM 11 sources came out. I haven't tried again since then. I might have another go but this time with CM 11. AOSP might be difficult but not impossible. Then again, I want my tweaks. At the same time though, it would be nice to have a clean, Nexus type of ROM, like a "Google Edition L9"
Sent from my LG-P769 using Tapatalk

---

ok im using propeitrary files this time im gonna test if it works

---

@artit by any chance if if's not any trouble for you, I was hoping I could ask how to create an Aroma version of a ROM installer. Any help is greatly appreciated, also thanks for MIUI

---

leolawliet said:
@artit by any chance if if's not any trouble for you, I was hoping I could ask how to create an Aroma version of a ROM installer. Any help is greatly appreciated, also thanks for MIUI
Click to expand...
Click to collapse
I also start using aroma by examine other dev works. These is what you have to do to use aroma installer.
1. Download it from http://forum.xda-developers.com/devdb/project/?id=330#downloads
2. Downloaded file is an example of aroma. Boot in to recovery and install it, you will see a lot of aroma features. You can create your own test file by copy some config from that file or maybe aroma file in my ROM.
3. Aroma script files are in /META-INF/com/google/android/
- aroma-config -> You use this config to create all dialog and pages in aroma
- updater-script -> Normal updater-script file. You can get aroma options and use it as conditional parameter
- update-binary -> this is aroma program
- update-binary-installer -> this is an original update-binary. If you want to use update-binary from CM or others rom please replace it with this file.
- aroma -> this folder contains resources. I use changelog.txt in this folder.
4. To add aroma to your rom
- In your rom, rename /META-INF/com/google/android/update-binary to update-binary-installer
- copy all aroma files to /META-INF/com/google/android/ (except update-binary-installer and updater-script)
- create you own aroma-config
- customize your updater-script to use options from aroma prop
5. If something go wrong while installing, aroma has an option to save install log to sdcard. You can review what is the problem in that log.
That's all. It's not hard to use aroma.
---------- Post added at 06:09 PM ---------- Previous post was at 06:00 PM ----------
Juanito216 said:
I attempted before CM 11 sources came out. I haven't tried again since then. I might have another go but this time with CM 11. AOSP might be difficult but not impossible. Then again, I want my tweaks. At the same time though, it would be nice to have a clean, Nexus type of ROM, like a "Google Edition L9"
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Nice try, I've tried to build AOSP 2 or more times but not success
I can build AOSP but it doesn't boot up. In logcat there're something wrong with display initialzation. I also try to use CM / AOKP build platform to build AOSP. But it has some libs conflict that I cannot solve.

---

i kept getting failed flashing zip, i was trying to port chameleon os for p760

---

keeps saying error in updater-binary

---

thasilenthacker said:
i kept getting failed flashing zip, i was trying to port chameleon os for p760
Click to expand...
Click to collapse
Some command in update-script is wrong or misplaced. It's hard to correct that. For me, I add some ui_print() to see what's the last step script run into and try to see what is the problem.

---

ok i found my problem at setting permissions
i used cm set_perm and still same thing its says " ste_perm: some changes failed

---

artit said:
I also start using aroma by examine other dev works. These is what you have to do to use aroma installer.
1. Download it from http://forum.xda-developers.com/devdb/project/?id=330#downloads
2. Downloaded file is an example of aroma. Boot in to recovery and install it, you will see a lot of aroma features. You can create your own test file by copy some config from that file or maybe aroma file in my ROM.
3. Aroma script files are in /META-INF/com/google/android/
- aroma-config -> You use this config to create all dialog and pages in aroma
- updater-script -> Normal updater-script file. You can get aroma options and use it as conditional parameter
- update-binary -> this is aroma program
- update-binary-installer -> this is an original update-binary. If you want to use update-binary from CM or others rom please replace it with this file.
- aroma -> this folder contains resources. I use changelog.txt in this folder.
4. To add aroma to your rom
- In your rom, rename /META-INF/com/google/android/update-binary to update-binary-installer
- copy all aroma files to /META-INF/com/google/android/ (except update-binary-installer and updater-script)
- create you own aroma-config
- customize your updater-script to use options from aroma prop
5. If something go wrong while installing, aroma has an option to save install log to sdcard. You can review what is the problem in that log.
That's all. It's not hard to use aroma.
---------- Post added at 06:09 PM ---------- Previous post was at 06:00 PM ----------
Nice try, I've tried to build AOSP 2 or more times but not success
I can build AOSP but it doesn't boot up. In logcat there're something wrong with display initialzation. I also try to use CM / AOKP build platform to build AOSP. But it has some libs conflict that I cannot solve.
Click to expand...
Click to collapse
Thanks, it's more simple than I thought it would be
Thank god I'm familiar with updater scripts

---

still cant get it to work. @artit you think you could modify this to run on our p769's?
http://forum.xda-developers.com/showthread.php?t=2508699

---

thasilenthacker said:
still cant get it to work. @artit you think you could modify this to run on our p769's?
http://forum.xda-developers.com/showthread.php?t=2508699
Click to expand...
Click to collapse
It's easier to port it to P768 because all I need to change is a firmware file. But for P769 you need to replace kernel so there maybe some incompatible issues. In AOSPA rom I also had problem when I replaced P760 kernel with P768 (from other rom). But when I build new P768 kernel for that rom it works.
I don't have P769 for testing so it's hard for me to port it to P769. Just wait for CM11 or maybe other ROM (AOKP/AOSPA). Most of its dev have paid a lot afford to new 4.4 version.

---

i am willing to be a tester if youd work on it, im online everyday

---

artit said:
The easiest way is
1. Replace kernel with working P769 kernel.
2. Replace all propeitrary files with P769 version. (You can have these files list from CM)
3. Add some more libraries (I don't know which files. I got brightness config doesn't working problem but I cannot solve it.)
I think that's all. Then you can add some customize to the rom. I used to port MIUI to P769 and that is what I did. But you may have some problem with some hardware library which is not in propreitary files list. It's an trial and error process but you need to have P769 to test it.
Click to expand...
Click to collapse
Has the brightness thing been solved yet? I am having this issue with a ROM that was "ported" but is incomplete because it completely lacks brightness control.