There's an unofficial build of Lineage OS 13 for KKBL available in the Razr HD section. As far as I know, this is the first build of Android 6.x or above that has been released on KKBL (which means 3.4.x kernel). So, two questions.
How many and what changes are required to get this working on XT907?
Has anyone already attempted this (and would like to provide feedback)?
@DiamondJohn, do you have any input on this? Would be interesting to try this out. Any idea what changes are required? Must be minor (screen density only?) I'm hoping at least...
rahimali said:
@DiamondJohn, do you have any input on this? Would be interesting to try this out. Any idea what changes are required? Must be minor (screen density only?) I'm hoping at least...
Click to expand...
Click to collapse
I'm, no crack dev, but the first thing I would look into are the differences in the device proprietary files, if they appear to be pretty similar devices.
XT925 = https://github.com/LineageOS/android_device_motorola_xt925/blob/cm-14.1/device-proprietary-files.txt
XT907 = https://github.com/LineageOS/android_device_motorola_xt907/blob/cm-14.1/device-proprietary-files.txt
For example, a big part of the "porting" of an xt897 ROM to an xt907 is held in the above info (and the relative locations of the actual binary files used with the same name). Its a starting point. I think someone converted a XT907 ROM to their xt925 using my above suggestion; but not perfectly.
When I first started building for my XT905 (ie a 907) I noted that there was already a device tree for the 907, but from memory, I think its for KKBL (im JBBL)
https://github.com/LineageOS/android_device_motorola_xt907
DiamondJohn said:
I'm, no crack dev, but the first thing I would look into are the differences in the device proprietary files, if they appear to be pretty similar devices.
XT925 = https://github.com/LineageOS/android_device_motorola_xt925/blob/cm-14.1/device-proprietary-files.txt
XT907 = https://github.com/LineageOS/android_device_motorola_xt907/blob/cm-14.1/device-proprietary-files.txt
For example, a big part of the "porting" of an xt897 ROM to an xt907 is held in the above info (and the relative locations of the actual binary files used with the same name). Its a starting point. I think someone converted a XT907 ROM to their xt925 using my above suggestion; but not perfectly.
When I first started building for my XT905 (ie a 907) I noted that there was already a device tree for the 907, but from memory, I think its for KKBL (im JBBL)
https://github.com/LineageOS/android_device_motorola_xt907
Click to expand...
Click to collapse
what about this one?
https://github.com/LineageOS/android_device_motorola_moto_msm8960
although i wouldn't know what to do with it since i'm no dev. you think you could somehow port the xt92x build to xt90x / msm_moto8960 devices?
rahimali said:
what about this one?
https://github.com/LineageOS/android_device_motorola_moto_msm8960
Click to expand...
Click to collapse
I have assumed that the source and the dest are both msm8960 devices, bo9th on the same level/ver of bootloader, and therefore this reads as a shared code path traversed by both devices, so its already taken care of (in both). You are looking for DIFFERENCES in the code path.
PS: the other thing you will need to modify is the "updater-script" (in particular the first line) and the build.props (it doesn't normally flash from the zip without extra instructions, even though "its there"). I have personally changed the first line of the updater script and then copied the firmware files and an updated build.prop within TWRP before my first boot for quick checks. Just use the set permissions to 755 for safety on each file as well (for testing)
I have been trying to build crDroid for xt907_JBBL, but have been having issues. Today I thought of upgrading to the KKBL, which made me then search and not find, a suitable TWRP (ie >= v3.x)
is there a xt907_KKBL TWRP >=3.x? or would I have to build one?
DiamondJohn said:
is there a xt907_KKBL TWRP >=3.x?
Click to expand...
Click to collapse
No. The last is 2.8.6
Shmaks said:
No. The last is 2.8.6
Click to expand...
Click to collapse
Can that flash Nougat ROM's?
DiamondJohn said:
Can that flash Nougat ROM's?
Click to expand...
Click to collapse
Who knows. The last custom rom for kkbl is cm12 and 2.8.6 flash it, so there is no way to check
Could you try the following sand let me know if it works?
https://forum.xda-developers.com/dr...p-twrp-xt907-kkbl-experimental-build-t3652716
DiamondJohn said:
Could you try the following sand let me know if it works?
https://forum.xda-developers.com/dr...p-twrp-xt907-kkbl-experimental-build-t3652716
Click to expand...
Click to collapse
Maybe i will try later today. But, what reason? Do you planning build nougat (or cm13) rom kkbl for XT907?
Shmaks said:
Maybe i will try later today. But, what reason? Do you planning build nougat (or cm13) rom kkbl for XT907?
Click to expand...
Click to collapse
I am trying to build crDroid v3.6 (ie 7.1.2), however for my JBBL its having numerous FC's I do have a zip file which would enable me to upgrade to KKBL which would make it interesting to see if a KKBL version is more stable. IF I could also SAFELY go back to JBBL I had a Moto X and accidently (by accepting an OTA) downgraded my bootloader and that caused a hard brick on the device, so I am a little cautious to say the least, as it is my daily.
I am also just downloading the device tree for an xt907 KKBL on my build machine and see if it can build a LineageOS 13. I'll let you know how it goes, and probably paste up a link for others to test if it succeeds to build since my device is JBBL
=============== edit =============
Correction, I am testing a Lineage OS 14.1 (ie Nougat) build of xt907 KKBL
DiamondJohn said:
IF I could also SAFELY go back to JBBL
Click to expand...
Click to collapse
For safely moving between kkbl-jbbl and backward i used flashbacks for along time:
https://androidfilehost.com/?fid=24533100289589621
https://www.androidfilehost.com/?fid=385035244224404260 (flash it in twrp, then firmware or custom rom on jbbl (kkbl) based)
Never had problems with them.
DiamondJohn said:
Correction, I am testing a Lineage OS 14.1 (ie Nougat) build of xt907 KKBL
Click to expand...
Click to collapse
Cool, hope for a successful experience
Shmaks said:
For safely moving between kkbl-jbbl and backward i used flashbacks for along time:
https://androidfilehost.com/?fid=24533100289589621
https://www.androidfilehost.com/?fid=385035244224404260 (flash it in twrp, then firmware or custom rom on jbbl (kkbl) based)
Never had problems with them.
Click to expand...
Click to collapse
Thanks, the links I found for these zips were all dead or required registration.
Shmaks said:
Cool, hope for a successful experience
Click to expand...
Click to collapse
Its at 4 % .., step 1512 of 34456 ... 5% and I'm off to bed, its late here. The big problem is uploading it to a host, its normally an over night job or at least a a few hours. So it may be two nights before its up somewhere to download IF it succeeds in da build.
9%....
11%...
DiamondJohn said:
Thanks, the links I found for these zips were all dead or required registration.
Click to expand...
Click to collapse
other (working) link https://www.dropbox.com/sh/791ixp14rqlzigo/AAAlNvQS3DGwzXv1AIeY0Fm2a
@DiamondJohn, I have the flashbacks to JBBL and KKBL available as well, lemme know if you want but the AFH links posted earlier work just fine as well.
Sorry I'm also on JBBL otherwise I would help you test your recovery. TWRP 2.8.x not compatible with Nougat?
Edit :: Do you think the XT907 has the horsepower to handle Nougat? I'd say the best best for this phone would be any flavor of MM but no higher. I'm on MoKeE Nougat JBBL and it seems to work well enough...
DiamondJohn said:
11%...
Click to expand...
Click to collapse
100%
It built successfully!:highfive: to be clear, I now have a LOS 14.1 (ie Nougat) ROM zip for an xt907 KKBL file, sitting on my disk. I will upload it (hours....) and post it up for someone (on KKBL) ...anyone... to try.
Shmaks said:
other (working) link https://www.dropbox.com/sh/791ixp14rqlzigo/AAAlNvQS3DGwzXv1AIeY0Fm2a
Click to expand...
Click to collapse
rahimali said:
@DiamondJohn, I have the flashbacks to JBBL and KKBL available as well, lemme know if you want but the AFH links posted earlier work just fine as well.
Click to expand...
Click to collapse
No need, because I have a an xt905, it has Australian frequencies, which means Australian specific modem. These zips were only for me to confirm the steps I plan to take when flashing manually using fastboot, from an Australian specific (ie xt905) Image file. so, one example is enough. Thanks anyway.
rahimali said:
Sorry I'm also on JBBL otherwise I would help you test your recovery. TWRP 2.8.x not compatible with Nougat?
Click to expand...
Click to collapse
I don't know. I know on previous version of Android, new versions of ROM zip files took advantages of features not in older TWRP images, and TWRP 2.8.x is getting old.
There is little drive in me building, uploading and posting a KKBL ROM post, if no-one else is testing it for me ie save me the hassle of flashing KKBL only to find TWRP &/OR ROM does not work. Yes, its all about me
rahimali said:
Edit :: Do you think the XT907 has the horsepower to handle Nougat? I'd say the best best for this phone would be any flavor of MM but no higher. I'm on MoKeE Nougat JBBL and it seems to work well enough...
Click to expand...
Click to collapse
More than enough. I have built a nougat ResurectionRemix and a crDroid (available HERE for testing; JBBL only) and it felt just as snappy as Marshmallow. Also, on my daily, I am running LOS13.0 with the Nougat Kernel, overclocked to 1.98GHz. ie we can also get a small/tiny boost easily with OC; the feature is built into the kernel but simply switched off in the LOS official builds.
DiamondJohn said:
100%
It built successfully!:highfive: to be clear, I now have a LOS 14.1 (ie Nougat) ROM zip for an xt907 KKBL file, sitting on my disk. I will upload it (hours....) and post it up for someone (on KKBL) ...anyone... to try.
Click to expand...
Click to collapse
Can't wait
Shmaks said:
Can't wait
Click to expand...
Click to collapse
have you tried TWRP for KKBL? And you may be waiting for a dud however upload is at 53%
DiamondJohn said:
have you tried TWRP for KKBL?
Click to expand...
Click to collapse
Yes, it works!
Related
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.
PonsAsinorem said:
Well, that's just not true. I use 2.6.3.4 to flash my ROMs (and radio when I don't RUU), and those ROMs are all 4.4.2.
But to answer your question OP, I don't know since I haven't looked at that part of the source. But I believe TWRP is the only supported recovery, so keep that in mind when thinking about bug reports and error messages.
Click to expand...
Click to collapse
Don't mind me...I forgot I was in the Omni boards and not my local device sub-forum
lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Skripka said:
All 4.4 ROMs only flash properly with CWM or Philz. Using TWRP will result in radios not working.
Click to expand...
Click to collapse
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.
Entropy512 said:
No. TWRP's configuration is more "self-contained" in terms of many of its build dependencies. CWM requires tentacles throughout the entire Android source tree over 4-5 or more projects that I'm not merging unless they can be proven to be needed for more than just CWM.
Um, TWRP is the only supported recovery for Omni. Most specifically, OpenDelta is GUARANTEED to fail with official CWM since Koush blocks advanced recovery scripting by anything other than ROM Manager.
TWRP works to flash Omni on every supported device I know of that's receiving nightlies. If this isn't the case on ANY device it's a pretty big bug the maintainer needs to address.
Click to expand...
Click to collapse
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
I've been flashing OmniROM on my Note II since the very first day only using TWRP. Before that not a single nightly zip of CM 10.1/2, PA or PAC was a problem.
Sent from my GT-N7100 using Tapatalk
lozohcum said:
Hello,
As in the title, how can I build OmniRom (KitKat) with CWM based recovery instead of TWRP?
I don't want TWRP, a lot.
Click to expand...
Click to collapse
Today I installed OMNI ROM 4.4.2 on Galaxy Note with CM 10.1 + CWM (6.0. ...)
- it works Ok.
Generally I followed the "Installing Omni on your device" instruction at docs.omnirom.org
- excluding TWRP installing
- I downloaded Google Apps for Android 4.4 from CyanogenMod site (gapps-kk-20140105-signed.zip)
Skripka said:
Yea well TWRP fails at flashing any 4.4 build (CM-base, Omni, etc) on at least the L900 Note 2 and possibly other Note2 devices. Whereas CWM/PhilZ is the only way. Been that way since CM first started pushing out 4.4 builds.
Click to expand...
Click to collapse
Only thing I can think of is TWRP is out of date and needs updating for that device, or there are updated TWRP builds and you're not running one.
lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
What does that have to do with this thread?
libm compiles just fine as it is in omni - if it didn't, then none of our nightlies would build
lozohcum said:
Thanks for reply!
I had problems with compiling libm, finally fixed by replacing bionic/libm folder with CM11 one.
I thought OmniRom is friendly source, now I've changed my mind, it's much more complicated than CM. I had no such problems with building CM11.
@Entropy512
Can TWRP damage my device? I don't know if my config is correct at all or if it's enough. This is my BoardConfig
Or can I use boot.img from CM11 instead of the one compiled with OmniRom?
Click to expand...
Click to collapse
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.
dibblebill said:
Complicated? Breakfast your device, and brunch it. Maybe use DonkeyCoyote's device binaries repository if needed (IIRC, even CM needs this), and that's about it. If you MUST use CWM, get PhilZ's, I hear he unblocked the advanced function calls.
Click to expand...
Click to collapse
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?
lozohcum said:
So can I just replace PhilZ recovery with TWRP?
Like he said in his thread just sync to bootable/recovery?
Click to expand...
Click to collapse
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.
dibblebill said:
That'd be my guess- don't forget to remove package in your local manifest.
EDIT: I misunderstood your question, so I apologize if I was overly harsh.
Click to expand...
Click to collapse
No problem. Thanks for replying, it helped me.
Once the first build is finished I'm going to change recovery.
lozohcum said:
No problem. Thanks for replying, it helped me.
Click to expand...
Click to collapse
If setting up the local_manifest gives issues, let me know- I can try to sort one out for you. I've replaced packages like Calculator, but never the recovery.
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?
Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
geowolf1000 said:
Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
Click to expand...
Click to collapse
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Just update to 28
geowolf1000 said:
Just update to 28
Click to expand...
Click to collapse
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
bingbinghaha said:
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
Click to expand...
Click to collapse
Let me guess, you were coming back to this kernel from Franco?
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
zaphodbeeb said:
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Click to expand...
Click to collapse
I can flash it or someone has a kernel update to the last nightly?
inscythe said:
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
Click to expand...
Click to collapse
I will try
I am doing this for my self but i want to share with xda friends
Thread update to 31
Amazing improvement to touchscreen
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
reyscott1968 said:
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
Click to expand...
Click to collapse
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
My wifi broke with this as well. Running completely stock 38R.
Can you share Source code please?
CrunchSA said:
My wifi broke with this as well. Running completely stock 38R.
Click to expand...
Click to collapse
Have you backup?
Just restore only system from revovery
Yeah, did that. Just reporting here that it was broken as an FYI.
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
Would this flash over Franco fine? Thanks in advance.
geowolf1000 said:
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
Click to expand...
Click to collapse
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
inscythe said:
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
Click to expand...
Click to collapse
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
geowolf1000 said:
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
Click to expand...
Click to collapse
If you see other custom kernel pages, usually they would have different versions for CM11 and CM11S... So I would assume that there are inherent differences between them. But if it is working fine for you, then great! Maybe I'll try it myself too
runderekrun said:
Would this flash over Franco fine? Thanks in advance.
Click to expand...
Click to collapse
Reflash (dirty) your ROM first to restore WiFi firmware
Download link removed. Please head over to N7105 thread now as developer is releasing builds for E250S and E250K as well.
what specific ril patch should we use on shv-e250k models?
Option58 said:
How to install Android 6 on Korean Note 2 devices:
Big thanks to @Strawberry_dev, he actually made this possible. He is the one to make a kernel to convert N7015 AOSP ROMs to Korean ones. Thank him (and ROM devs), this is NOT my work! I just wrote this tutorial.
I strongly recommend this to everyone. Way better than Samsung 4.4. It literally saved me from a buying new device. It's really fast and up to date. Suitable for use in 2016.​
Click to expand...
Click to collapse
Stuck on bootloop​
axl1234 said:
what specific ril patch should we use on shv-e250k models?
Stuck on bootloop
Click to expand...
Click to collapse
Ril patch not needed.
Option58 said:
Then I guess this doesn't work for E250K very well. Can someone share experiences?
I've only tested this on my E250S.
Click to expand...
Click to collapse
sir.do you have any links for the files that you used?especially the RIL patch. i did follow the instructions but I had problems downloading the ril patch. if you could upload it through mediafire or any cloud servers. that would be great. I guess what causes my SHV-E250K to bootloop is that the RIL patch was not flashed and it stucked on the Cyanogen Icon
Note 2 E250S - unable to get wifi working
I now have everything working except wifi. I downloaded the wifi mac address patch, but it didn't help. Is there an app I can use for the wifi? Or an alternative patch to download and flash? Thank you.
Freddy1950 said:
I now have everything working except wifi. I downloaded the wifi mac address patch, but it didn't help. Is there an app I can use for the wifi? Or an alternative patch to download and flash? Thank you.
Click to expand...
Click to collapse
That's very strange. Wifi should work. When I flash roms for N7100, N7105, etc. wifi works every single time.
The only thing that comes to my mind is that you weren't running latest firmware prior to installing this.
Forget Android 6 and go to Android 7. From Android 4.4, just follow the steps in the 1st thread, but do not install Widzard Kernel 2.7 & Gapps for 6.0. Then, download and dirty install any Android 7 ROM for N7105 and the corresponding GAPPS. Please note than Widzard Kernel does not seem compatible with Android 7. The Kernel included in the Android 7 ROM is enough for Korean Galaxy Note 2 (mine : SHV-E250S).
vincentru said:
Forget Android 6 and go to Android 7. From Android 4.4, just follow the steps in the 1st thread, but do not install Widzard Kernel 2.7 & Gapps for 6.0. Then, download and dirty install any Android 7 ROM for N7105 and the corresponding GAPPS. Please note than Widzard Kernel does not seem compatible with Android 7. The Kernel included in the Android 7 ROM is enough for Korean Galaxy Note 2 (mine : SHV-E250S).
Click to expand...
Click to collapse
True :good: But vibrator not working yet on E250S...On the other hand, widzard kernel has problem recording video so without it that will work.
Option58 said:
That's very strange. Wifi should work. When I flash roms for N7100, N7105, etc. wifi works every single time. This Widzard patch is intended to fix vibration.
The only thing that comes to my mind is that you weren't running latest firmware prior to installing this. Also some mac wifi fixes actually break wifi. For our device it is murata.
Click to expand...
Click to collapse
I have the wifi working fine now. Thank you. I am not sure what I did to get it working. Thanks.
---------- Post added at 06:49 AM ---------- Previous post was at 06:42 AM ----------
Option58 said:
That's very strange. Wifi should work. When I flash roms for N7100, N7105, etc. wifi works every single time. This Widzard patch is intended to fix vibration.
The only thing that comes to my mind is that you weren't running latest firmware prior to installing this. Also some mac wifi fixes actually break wifi. For our device it is murata.
Click to expand...
Click to collapse
Option58 said:
True :good: But vibrator not working yet on E250S...On the other hand, widzard kernel has problem recording video so without it that will work.
Click to expand...
Click to collapse
I can just dirty boot now to Nougat? Using N7105?
Freddy1950 said:
I can just dirty boot now to Nougat? Using N7105?
Click to expand...
Click to collapse
Yes. But I honestly don't have any idea how to fix vibration motor for E250S. So far N7105 Nougat builds are ok.
Edit: vibration fixed
N7105 for E250S
Option58 said:
Yes. But I honestly don't have any idea how to fix vibration motor for E250S. So far N7105 Nougat builds are ok.
It would be cool if Widzard kernel dev updated it to Nougat. But that's still not LinaegeOS original kernel.
Click to expand...
Click to collapse
I cannot find an N7105 Nougat ROM, I can only find for N7100. Is there an N7105 ROM? or do I just use the N7100?
Thank you so much for all of the help.
Freddy1950 said:
I cannot find an N7105 Nougat ROM, I can only find for N7100. Is there an N7105 ROM? or do I just use the N7100?
Thank you so much for all of the help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-2/development-n7105/rom-lineageos-n7105-t3538310
I do have shv-e250k... will any of these roms you are talking about works in my device? I tried installing installing a lot of roms however it always stuck on bootloop..I hope someone will answer...thank you
axl1234 said:
I do have shv-e250k... will any of these roms you are talking about works in my device? I tried installing installing a lot of roms however it always stuck on bootloop..I hope someone will answer...thank you
Click to expand...
Click to collapse
Yeah, they will.
Can anyone help me to upgrade note 2 e250s to marshmallow?
Option58 said:
https://forum.xda-developers.com/galaxy-note-2/development-n7105/rom-lineageos-n7105-t3538310
Click to expand...
Click to collapse
Thanks! I now have Nougat installed on my Note 2 E250S. It's great! Just love it.
Good news. I've finally got vibration to work on my E250S. Started building LineageOS 14.1 myself from now on.
Please test this on your E250L and E250K and we'll see if we can get things working for you.
Option58 said:
Good news. I've finally got vibration to work on my E250S. Started building LineageOS 14.1 myself from now on.
Please test this on your E250L and E250K and we'll see if we can get things working for you.
Click to expand...
Click to collapse
Congrats on finally fixing this. I know it was a long hard fight for you :good:
Option58 said:
Then I guess this doesn't work for E250K very well. Can someone share experiences?
I've only tested this on my E250S.
Click to expand...
Click to collapse
bro i m using lineage os unoffical rom by poisonNinja bro on my samsung galaxy note 2 e250k
it work fine for me all clear
Hi,
I've been kind of out of the loop for a bit, but after some problems with official ROMS i decided to switch to the custom ones.
I'm looking for something that's as stable and lag free as it can get (I was very happy with official roms from xiaomi to give you an idea of "good enough" for me).
Anything symilar available? I'm currently sitting on https://forum.xda-developers.com/redmi-4-prime/development/rom-aicp-13-t3752647 , but I see some minor stuttering and it happened to freeze for me already :/
I don't care about customization and fancy stuff, neither do i care about android version (as long as it's not ancient xD). Can anyone suggest something?
Wiral said:
Hi,
I've been kind of out of the loop for a bit, but after some problems with official ROMS i decided to switch to the custom ones.
I'm looking for something that's as stable and lag free as it can get (I was very happy with official roms from xiaomi to give you an idea of "good enough" for me).
Anything symilar available? I'm currently sitting on https://forum.xda-developers.com/redmi-4-prime/development/rom-aicp-13-t3752647 , but I see some minor stuttering and it happened to freeze for me already :/
I don't care about customization and fancy stuff, neither do i care about android version (as long as it's not ancient xD). Can anyone suggest something?
Click to expand...
Click to collapse
Try miracle Droid from razziel, very stable and it's still maintained.. As you can see this rom has the latest September security patch
How to update miracle droid?
yuba15 said:
Try miracle Droid from razziel, very stable and it's still maintained.. As you can see this rom has the latest September security patch
Click to expand...
Click to collapse
I used m droid build 20180907. I want to update to build 20180916. Can you help me to give me some way?
entolla9 said:
I used m droid build 20180907. I want to update to build 20180916. Can you help me to give me some way?
Click to expand...
Click to collapse
Just wipe dalvik, cache and flash latest version. No data will be lost, unless you wipe system, data.
How to update treble ROM
Thanks dude, i do what you say and it work..
I'm also interested in a stable rom. But i have to be sure first because i have to recover all my data and that sucks xDD
Can somebody asure which rom is the more stable? THX
Rafudus said:
I'm also interested in a stable rom. But i have to be sure first because i have to recover all my data and that sucks xDD
Can somebody asure which rom is the more stable? THX
Click to expand...
Click to collapse
For now, Mdroid Oreo is most stable among custom ROMs available for markw.
does anyone have a video problem on last mdroid oreo... i have only sound
Sent from my [device_name] using XDA-Developers Legacy app
kibria.mgk said:
For now, Mdroid Oreo is most stable among custom ROMs available for markw.
Click to expand...
Click to collapse
Okay, that's an statement, I want to know why is more stable and why there are only 3 users talking about this one rom.
And i can't even find the freaking post of the rom only links to the zip.
Rafudus said:
Okay, that's an statement, I want to know why is more stable and why there are only 3 users talking about this one rom.
And i can't even find the freaking post of the rom only links to the zip.
Click to expand...
Click to collapse
It's more stable because it's maintained more frequently, new builds are released as soon as the sources are updated.
And, there's no post about it on xda, it's maintained by a Russian dev and publishes his work on 4pda. So, you'll only get the zips. For details, follow him there.
kibria.mgk said:
It's more stable because it's maintained more frequently, new builds are released as soon as the sources are updated.
And, there's no post about it on xda, it's maintained by a Russian dev and publishes his work on 4pda. So, you'll only get the zips. For details, follow him there (I'll add 4pda thread link later).
Click to expand...
Click to collapse
Ok THANKS
Is it in english at least? I'm spanish so if the rom is in russian... Then I can't have it.
How is it flashed? I have the twrp treble so... Do I need to back up, wipe system, cache, dalvik, data... Flash the rom, gapps and magisk?
Is it right?
Rafudus said:
Ok THANKS
Is it in english at least? I'm spanish so if the rom is in russian... Then I can't have it.
How is it flashed? I have the twrp treble so... Do I need to back up, wipe system, cache, dalvik, data... Flash the rom, gapps and magisk?
Is it right?
Click to expand...
Click to collapse
The site is Russian, rom is in English. Flashing is as usual, as you described.