[Q] Android L Preview boot.img - AT&T LG Optimus G

Note: This is my first time trying to port or build a ROM for my phone, so I apologize if this is a stupid question.
I want to try to port the preview from the Nexus 4 (http://forum.xda-developers.com/nexus-4/development/lpv-79-mako-port-beta-t2807446) and I am trying to achieve this by using defcondev's tutorial (http://forum.xda-developers.com/showthread.php?t=2442593).
The third step of the process is to swap out the N4 boot.img with an OG boot.img. Would I be able to use a KitKat boot.img or would it have to be specifically designed for the L preview? If it has to be specifically built for L how would I be able to obtain it?
I'm just an everyday Joe with absolutely no programming knowledge trying to port L to my phone.
BTW I haven't seen anything about L for this phone, is no one else as excited for L as I am?
Thanks in advance!

A
I may be wrong dut heard that since 4.4+ appears it's much harder to port roms from nexus 4 without major changes, almost impossible...

ilya39 said:
I may be wrong dut heard that since 4.4+ appears it's much harder to port roms from nexus 4 without major changes, almost impossible...
Click to expand...
Click to collapse
Well I guess the hard working devs will port it over soon enough, KitKat until then.

At least porting kitkat will be a great progress, and then may be possible L porting

Related

Sense 4.0 Multitasking port help needed.

So i saw that in other devices fourms they ported the Sense 4.0 multitasking screen. But it's not working for all devices or builds.
So a dev/ or user has to port the code to our builds . I myself don't have the time to port it but i am looking forward to seeing this on out beloved device.
Here's the source thread. http://forum.xda-developers.com/showthread.php?t=1589963
Deonix said:
So i saw that in other devices fourms they ported the Sense 4.0 multitasking screen. But it's not working for all devices or builds.
So a dev/ or user has to port the code to our builds . I myself don't have the time to port it but i am looking forward to seeing this on out beloved device.
Here's the source thread. http://forum.xda-developers.com/showthread.php?t=1589963
Click to expand...
Click to collapse
It's quite easy I have this running now on my defy ...... U need to source code to apply no porting necessary
I will help you make one for yourself after my exams are done
There's already a thread that has a flashable zip that works for older nightlys.
it may look neat but it hardly promotes multitasking that the inbuilt ics carousel provides...you can barely see the next two open apps using the sense "multitasker"
Kayant said:
It's quite easy I have this running now on my defy ...... U need to source code to apply no porting necessary
I will help you make one for yourself after my exams are done
Click to expand...
Click to collapse
Thanks. I have exams as well ) i will try to port it. If i stumble i will let you know. Maybe i will like it.
Good luck on your exams.

Porting htc one roms to the max?

hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
+1
Sent from my SM-N900V using Tapatalk
hectorz321 said:
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
Click to expand...
Click to collapse
Permission failure? Noob here too
I am guessing the ROM you tried to port checks for the Model number of the phone before flashing. What ROM did you try to port to and if you could post the instructions here we will make this the porting thread
Given that HTC One has all the custom ROM's and kernels we need devs or someone like us who can follow instructions to start doing it. I am sure we will get help from one another and end up with custom ROM's for the MAX.
I was also thinking of doing this but just to start with i don't want to look at the fingerprint scanner and may be later we could get it working.
I am certain most people would be willing to not have a working fingerprint scanner, as a trade off for a few custom roms/kernels...
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Murrda said:
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Click to expand...
Click to collapse
this was exciting to read, best of luck
I am going to get Ubuntu installed today and then Android Kitchen here i come!
pradeepvizz said:
I am going to get Ubuntu installed today and then Android Kitchen here i come!
Click to expand...
Click to collapse
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
DeadPhoenix said:
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
Click to expand...
Click to collapse
Thanks, i just installed it via virtual box without disturbing my system.
Just got android kitchen up and running, on prting sides of things got further this time, into aroma installes but error 7 which suggested earlyer is to do with mount points, if anyone could happen to help with theese it would be fab ))
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Click to expand...
Click to collapse
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
pradeepvizz said:
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
Click to expand...
Click to collapse
Murrda said:
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
Click to expand...
Click to collapse
heyy i could use some help doing this part in android kitchen. straight from android kitchens page but i can't seem to get the recovery.fstab out anyway! im on t6ul verson of the max by the way thanks
/HIDE (sorry dont know how to get this to work (forum noob here too)
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
hectorz321 said:
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
Click to expand...
Click to collapse
Good start mate! awesome!
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
hectorz321 said:
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
Click to expand...
Click to collapse
Which guide are you following? i just cooked a ROM today first time. I made the stock ROM for the T6UL.
---------- Post added at 08:34 PM ---------- Previous post was at 08:34 PM ----------
ooo, Merry Christmas everyone
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
HolyAngel said:
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
hectorz321 said:
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
Click to expand...
Click to collapse
Yeah, i know for the kernel, without being able to mess with the zimage, the sense max kernel lacks the init.environ.rc from gpe, the fstab file is different(at least file extension), and there's a few things that point to sense files or folders that don't exist on gpe. Currently there is no released source for the max yet :'( so unless someone knows how to do it manually and hasn't shared HOW to do so, I just have to wait.. Hopefully it won't be too long.
Sent from my HTC One using XDA Premium 4 mobile app

[Q] New to rooting: Vanilla Android?

So I'm very new to rooting devices. I have a t mobile galaxy s5, and I want to run vanilla android on it. Preferably, I would also like to be able to download the developer version of android L, and then the full version when it releases straight from google. I have a guide to auto root this phone. I want to be able to back it up so I can reload touchwiz if something goes wrong. I may have to turn this phone into t mobile at some point, so this is crucial. I also would like to carry over my phones contacts with me into the vanilla build. Can anyone assist me? Sorry for my ignorance; I'm trying to learn. Thanks for your time.
I think you're out of your league.. for this to happen, you would need to get the Google source for android l then you would need the kernel source for android l for our devices (which doesn't exist, yet). I think if you really want android l you would need a Google device. You could also wait till cyanogen comes out with an android l version.
Sent from my SM-G900T using Tapatalk
Wow if we could do this it would be amazing. Really. Sadly we can't do anything close to this...sorry to dissapoint you.

[Q] Would someone do Android L porting?

Hi guys,
That's my first tread on xda.
The question is "Would someone do Android L potring??" Obviusly on our GT-i9300.
I'm not telling that i want a porting now but i'm afraid that this device will die after the 5.0 update.
So you good developers would you do the android 5.0 porting For us?
Bye.
+1
Inviato dal mio GT-I9300
Android L is still not yet fully developed by Google and thus it is a developer preview and is not suitable to be a daily driver rom. Maybe try asking after Google release Android L as an official update.
Sent from my GT-I9300 using XDA Free mobile app
well ports are already happening for some devices(n7 2k12 for instance)
but i doubt it will for s3, in fact i doubt we will even receive L (unofficialy)
it tooks months to get fully hw support in Kk thanks to closed source drivers
it took almost a year to fully fix the áudio driver (this one we already have a open source version of it)
and so on. also we are running 4.1+ on a "hacky" way (4.1 was meant for 3.1+ kernel, we have 3.0.101)
yet still, because of drivers we can´t achieve full speed(animations are quite bad) on custom roms, and thats with roms with same version as of Samsung).
but if we get, will be in october when the full release comes
The Android L preview image is not complete and is intended for devs for Nexus devices. A lot of things are missing.
We will have to wait till later this year for a port (if someone does it).

PORT Sense to another phone

Hello , i have 1 question can it be work if i port a Sense rom to my honor 8 ?
beacouse i love the Sense ui and the look i will be great if i see a sene rom for my phone
When you know the HTC HD2 and they have done to make a windows phone to an android phone with a lot of roms like Sense,Miui,AOKP, or PAC man rom then
at can be done with another one
The problem is, that it is really hard to build ROMs for devices with Kirin Chipset, because Huawei won't release any helpful source code. We can be lucky that they released some Kernel sources for several devices. Some honor and Huawei devices are nearly the same and ROMs that are build for one device, work on others with the same Chipset as well, so go and look if you find any, I think the OpenKirin released something for the honor 8/ the Huawei version. Just search your Chipset here on xda, you should find something. But there won't be a Sense ROM, I'm pretty sure.
EDIT: There is RROS available for your device!
You have to follow every single instruction, or some features won't work. That's probably everything you will get for that device.
Here is the link: https://forum.xda-developers.com/honor-8/development/rom-t3606257
GAMEthe said:
Hello , i have 1 question can it be work if i port a Sense rom to my honor 8 ?
beacouse i love the Sense ui and the look i will be great if i see a sene rom for my phone
When you know the HTC HD2 and they have done to make a windows phone to an android phone with a lot of roms like Sense,Miui,AOKP, or PAC man rom then
at can be done with another one
Click to expand...
Click to collapse
Simple answer is no. Sense like TouchWiz and all other oem distros rely on their own frameworks files that are closed Sourced and only compatible with their devices.
As for the HD 2. That was the last great device of its kind with a really open bootloader.

Categories

Resources