My question is can I use a devices stock kernel to create a build for said device?
My T-Mobile Sony Xperia Z has a locked bootloader and can only run roms using the stock kernel. I've seen other AOSP looking roms run off a devices stock kernel so I was hoping it possible.
Can anyone guide me in this? I would love for my phone to have HALO and different modes like phablet or tablet mode from Paranoid Android. Is this possible with a stock kernel or would features like that require a custom one? I assume it could be run just like Facebook Messenger does it..just as an app I mean.
knightsray said:
My question is can I use a devices stock kernel to create a build for said device?
My T-Mobile Sony Xperia Z has a locked bootloader and can only run roms using the stock kernel. I've seen other AOSP looking roms run off a devices stock kernel so I was hoping it possible.
Can anyone guide me in this? I would love for my phone to have HALO and different modes like phablet or tablet mode from Paranoid Android. Is this possible with a stock kernel or would features like that require a custom one? I assume it could be run just like Facebook Messenger does it..just as an app I mean.
Click to expand...
Click to collapse
Why do you think this isn't done already if it was this easy? The PA, CM framework and such needs code in the kernel and the stock kernel can't be remade because nobody's got the signing code for it, except Sony.
You'll need a unlocked bootloader for Omni ROM.
@MikeChannon, I think this thread can be closed.
Skickat från min C6603 via Tapatalk 2
TheHawk002 said:
Why do you think this isn't done already if it was this easy? The PA, CM framework and such needs code in the kernel and the stock kernel can't be remade because nobody's got the signing code for it, except Sony.
You'll need a unlocked bootloader for Omni ROM.
@MikeChannon, I think this thread can be closed.
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
You're wrong. It's not impossible to use stock kernel with a custom ROM, sometimes it's even inevitable, because there are no kernel sources available or the bootloader cannot be unlocked.
Adam77Root said:
You're wrong. It's not impossible to use stock kernel with a custom ROM, sometimes it's even inevitable, because there are no kernel sources available or the bootloader cannot be unlocked.
Click to expand...
Click to collapse
It's pretty much impossible to do so with an AOSP-based firmware. Occasionally it's tried, but always leads to poor results (see CM9 ICS builds for I9100 prior to kernel source release that used an initramfs repack.)
At a minimum it requires initramfs changes, and since the initramfs is signature-checked as part of the kernel image on every device I know of, it's not possible without terrible terrible hacks. Personally, I would prefer to not bother at all supporting any locked device that requires workarounds in the build. It leads to difficult to maintain code, and if people want to run an open source firmware, they should just not buy a locked (or non-unlockable) device in the first place.
Entropy512 said:
It's pretty much impossible to do so with an AOSP-based firmware. Occasionally it's tried, but always leads to poor results (see CM9 ICS builds for I9100 prior to kernel source release that used an initramfs repack.)
At a minimum it requires initramfs changes, and since the initramfs is signature-checked as part of the kernel image on every device I know of, it's not possible without terrible terrible hacks. Personally, I would prefer to not bother at all supporting any locked device that requires workarounds in the build. It leads to difficult to maintain code, and if people want to run an open source firmware, they should just not buy a locked (or non-unlockable) device in the first place.
Click to expand...
Click to collapse
I also prefer having sources and building kernels rather than doing bad hacks, I just pointed out that it's possible and sometimes is a must (Not talking about Omni, just in general.), there are devices without unlockable BL. E.g. we were using 2nd-init method on p880 before official JB came out and BL unlock became possible.
Adam77Root said:
I also prefer having sources and building kernels rather than doing bad hacks, I just pointed out that it's possible and sometimes is a must (Not talking about Omni, just in general.), there are devices without unlockable BL. E.g. we were using 2nd-init method on p880 before official JB came out and BL unlock became possible.
Click to expand...
Click to collapse
May I ask if you ever had a AOSP based firmware or just remakes of the stock ROM to look like AOSP? Because there you've the big difference. It's (obviously, because Entropy is Entropy ) just like @Entropy512 said.
Skickat från min C6603 via Tapatalk 2
TheHawk002 said:
May I ask if you ever had a AOSP based firmware or just remakes of the stock ROM to look like AOSP? Because there you've the big difference. It's (obviously, because Entropy is Entropy ) just like @Entropy512 said.
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. I know the difference between a themed and a real AOSP rom. If I didn't, I wouldn't be a RD. What I wrote is totally possible and legit.
Sent from my OmniROM-powered LG Optimus 4X HD
Related
Hi, I was just curious to know what the benefits of a cracked boot loader is and what features we could implement or achieve that we already have.
With this we should put custom kernels on our devices, and this way we should eliminate major bugs with GingerBread and Froyo, since some of stuff are made with patches over stock libs (I´m not certain about that, but it was what I understood while reading some threads). By the way, tethering over cyanogenmod menu, is only possible if we get custom kernel, if I´m not wrong doixahn said that. To end it up, with bootloader cracked, we may hope for more stability over our devices
biscoitu said:
With this we should put custom kernels on our devices, and this way we should eliminate major bugs with GingerBread and Froyo, since some of stuff are made with patches over stock libs (I´m not certain about that, but it was what I understood while reading some threads). By the way, tethering over cyanogenmod menu, is only possible if we get custom kernel, if I´m not wrong doixahn said that. To end it up, with bootloader cracked, we may hope for more stability over our devices
Click to expand...
Click to collapse
thanks, but what do you mean by a custom kernel?
_Sparks said:
thanks, but what do you mean by a custom kernel?
Click to expand...
Click to collapse
a kernel is the linux core containing drivers for all the hardware. Basically if we crack it we can add drivers for camera for example and make it work say face detection or autofocus or whatever from any other device drivers (like X10) plus adding the lib's straight into kernel not patching in and out
ahmedz_1991 said:
a kernel is the linux core containing drivers for all the hardware. Basically if we crack it we can add drivers for camera for example and make it work say face detection or autofocus or whatever from any other device drivers (like X10) plus adding the lib's straight into kernel not patching in and out
Click to expand...
Click to collapse
Yeah,...and devs cam make kernel even it smaller if they want a very thin r0m
ahmedz_1991 said:
autofocus
Click to expand...
Click to collapse
lulz nope
10characters
Probably X8's camera is to weak to handle autofocus.
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv500
Is where you can get it (start your downloading now...)
the strange thing is they appear to have two uploads for kitkat...
Sent from my LG-V500 using XDA Premium HD app
Yay! What does it mean for the simple user? Better roms?
Sent from my iPhone using Tapatalk
All I really want is gamma correction and maybe overclocking and U/V.
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
muiriddin said:
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
Click to expand...
Click to collapse
The first and most obvious is the gamma set at 2.05 roughly. If you set it to 2.2 - 2.3, that would already be a big plus.
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Good to hear that someone else contacted them as well. I have been impressed with their open source group responding as quickly as they did. They definitely respond better than several other companies when facing these requests!
:good::good: I would pay anybody to incorporate or activate the OTG+Charging in this Kernel. :good::good: :fingers-crossed:
id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
LBJM said:
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
Click to expand...
Click to collapse
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
I compiled a kernel using the source provided by LG, but for some reason, it doesn't boot.
I keep getting this error:
Code:
Secure booting error
Cause: boot certification verify
I noticed that the resulting "boot.emmc.win" is a lot smaller than the original boot.emmc.win (~10 MB compared to 24MB)
Another interesting thing is that if I uncompress the original 24 MB boot.emmc.win using the command "unmkbootimg -i boot.emmc.win", I get two files: kernel (7.5 MB) and ramdisk.cpio.gz (2.6 MB). If I rebuild the boot.emmc.win using these exact two files, I get an 11MB boot.emmc.win, but this one DOES boot.
It probably has something to do with the locked bootloader and the loki exploit.
Can anyone help me get to the bottom of this? I really want to solve the gamma issue.
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Canadoc said:
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Panel is very close to correct gamma when using default linear qlut, instead of MSM_MIPI_LGIT_VIDEO_WUXGA_PT_PANEL qlut.
I would definitely take a look at the 50018A kernel if someone can provide the source. I wasn't able to find it.
gin_silver said:
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
Click to expand...
Click to collapse
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
LBJM said:
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
Click to expand...
Click to collapse
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
gin_silver said:
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
Click to expand...
Click to collapse
Good to know.
20d source released
I do not know if anyone will find this of use, but they have now posted the 20d kernel source (and some other stuff).
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Hello ruxandy,
Can you explain in few words how did you manage to push the kernel to your v500?
Here is my story:
I downloaded the V500 Lollipop kernel because I wanted to compile .ko loadable modules and drivers to support RTL2832U DVB USB dongle. I successfully compiled those modules, rooted the tabled and tried to insmod them. But it failed because the modules did not find some kernel APIs.
Then I decided to build the kernel with built-in those drivers and I did it successfully, the problem now is what to do with zImage. I read there are two roads the one building own KDZ file seems very complicated and not sure if really possible. The other seems to be to extract the boot.emmc.win file using TWRP. So I downgraded the V500 bootloader from LT to KK and installed TWRT using this http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846 but after reboot got the secure boot error you did.
So again - how to use self built zImage and is this possible for KitKat only, since installing TWRP with Lollipop does not seem possible so far?
The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.
Oh Gr8 news ! Hope we could get custom kernel on OPO soon
Sent from my One using XDA Premium 4 mobile app
I am hoping we get one soon also.
Sent from my One using Tapatalk
SferaDev said:
The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.
Click to expand...
Click to collapse
Mind putting together the flashable zip of the stock kernel so that users who go custom kernel flashing (Franco for now) can fall back to the stock kernel?
A flashable .zip would be great
@SferaDev Thanks for this, I will be using this to build a kernel for our devices
Gamma control is out:
0f98e789af8c12ce3687cbe4515b429aa1e031a3 video: mdss: Add predefined gamma selection
I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?
DrDaxxy said:
I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?
Click to expand...
Click to collapse
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...
SferaDev said:
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...
Click to expand...
Click to collapse
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?
DrDaxxy said:
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?
Click to expand...
Click to collapse
I haven't faced ANY kernel that doesn't work...
A flashable zip will be great! Can any expert help on this?
http://developer.sonymobile.com/201...-aosp-for-xperia-on-github-video-open-source/
Enjoy
I wonder if camera and modem will be supported in the future.
well thats good news
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Yeah we already knew because author already posted here http://forum.xda-developers.com/showthread.php?t=2907471
Sent from my D6503 using Tapatalk
Felimenta97 said:
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
I'd argue it's an official release - a release for developers, but it's still official.
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
funky0308 said:
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
Click to expand...
Click to collapse
I see this too much... Aka agreement on ur post
And secondary point,
Not a rom, its neither a aosp rom
Yes official but its purely there for CM11, AOSP and any deviant developers to correct problems with their builds or correcr sonys problems
Its a greed thing sony is doing, it will benefit sony as well as xda devs
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Cigaras said:
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Click to expand...
Click to collapse
Unlocked bootloaders ONLY. If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void, thus creating problems for Sony, with non Devs users returning phones and help queries etc...
waynekirby said:
If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void
Click to expand...
Click to collapse
But if AOSP is provided by Sony themselves, why would they threat it as warranty voiding?
Lets take for example Xiaomi, for Mi3 and Mi4 gsmarena.com said that You could choose either MIUI or AOSP, and You get OTA updates for both (I am not sure if that is official, I do not own a Xiaomi device). Would be great if Sony would do something similar, Google Play Edition would also work for me, as long as I get to keep all the Bravia Engine and X-Reality goodness
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
I highly doubt this. If it's true, you should be able to show that, though...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
adyscorpius said:
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
Click to expand...
Click to collapse
I don't understand your point here...
I know there are differences, that's why Sony works on this, officially.
We have CM and AOSP ROMs for Z1/Z2 but Sony now hired guy from here to help them in building AOSP that'll work on LB and is released by Sony.
That way, they still can control and approve what will go to device abd what won't...
Maybe I'm wrong but what's the point of releasing AOSP without kernel support from bootloader?
We already have that..
My guess would be - they want us to use AOSP but they don't want us to unlock bootloader and mess with DRM keys.
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
funky0308 said:
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
Click to expand...
Click to collapse
Would be nice if instead of your warrenry being voided, its changed
So free repairs for sony fauls so long as its not caused by you rom
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Haldi4803 said:
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Click to expand...
Click to collapse
We only are getting source it seems but to have this for locked bootloaders sony must compile and sign a rom and kernel
Yo peeps,
Code:
[COLOR="Red"]For people who say I will wait for official update STAY OUT![/COLOR]
So i was trying to port the G2's Lollipop update to G1. Many of you may think itz quite useless, well i just decided to try because i am a big dev here to compile AOSP or CM12 roms without a proper device tree. So while we wait for Official Update or until CM/AOSP becomes stable i thought maybe i could try porting. So i managed to get the system and boot.img made a zip and now the problem seems with the kernel. I get a fall through to fastboot mode when i use their kernel and when i use ours it gets stuck on bootlogo. Both the kernels are of 3.4.42 and i am not good at kernels like the way i am at kang so if someone could help me with the kernel part maybe we can get L earlier.
This thread is for only people who can encourage and try helping! Others please excuse.
I unpacked both the boot.img made a zip of it and uploaded so that it would be easier for people to help. I dont mind testing it numerous times. Willing to listen and try anything and everything that can make it boot. So here are the kernels.
Hope to find help!
@VictoriousShooter
@rr46000
@S0bes
@yajnab
I think it is impossible without kernel source... This way you can play with Ramdisk only. Moto g2 has little bit different hw..
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
AgentChaos said:
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
Click to expand...
Click to collapse
The ROM itself-yes
Kernel-no.
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Justice™ said:
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Click to expand...
Click to collapse
cm kernels wouldnt work on stock roms bro.. tried it.
fabus said:
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Click to expand...
Click to collapse
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
@S0bes i thought you may know something so kinda tagged u bro btw i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
yeshwanthvshenoy said:
i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
Click to expand...
Click to collapse
I do not believe so. Neither Android 4.4.4 Moto G LTE nor, Moto G (2014) Kernels (or ROMs) boot on Moto G (2013.)
@yeshwanthvshenoy I know you stated you are a big dev, but since you are, you already know kernels can't be ported from an image. You need the source code. Unless you have a magical way of changing code without needing to decompile.
Still... if you are having fin making zips, go ahead, don't let my words discourage you. But... this is a dead end.
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
reversegear said:
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
Click to expand...
Click to collapse
I dont think there will be any luck since G 2014 has a different MSM board and that has to do with the result you will get. So if you manually flash XT1064 firmware on an XT1032 just expect a beautiful soft brick in the best of the cases... Just wait for official OTA, there are just days left for it!!! Next week we will se some news.
for this you need a new kernel for G1, which we dont have. (and even if we had it then we had the ROM too)
you will have to use the old kernel with the new ROM. which will obviously create tons of error.
have you tried CM12 kernel with the ROM?
For the kernel, try following and check if there is some progress.
Decompile both the kernels with dsixdia kitchen. You will get ramdisk and Zimage for each kernel. Try following combination.
4.4.4 Zimage (G1) + 5.0 Ramdisk (G2) + Modules (G1)
If no, try using init.rc of G1 and give another try.
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Somcom3X said:
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Click to expand...
Click to collapse
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
fabus said:
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
Click to expand...
Click to collapse
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Good luck on the kernel. Though I highly suspect that Motorola will give us Lollipop on the Moto G before anyone is able to come up with a working port.
Somcom3X said:
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Click to expand...
Click to collapse
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Get the basic source of the G1. Match the changes made to G2 for the L. Best to getthe old G1 kernel source and modify the things needed for the L. Test and Go.
Unless its creating changes in filesystem its good to play with.
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
yeshwanthvshenoy said:
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Click to expand...
Click to collapse
G2 device board name differs. It will be just foolish and waste of time