FOR EVERYONE:
The ROM IS NOT BOOTING YET. This thread is for DEVELOPERS ONLY, if you can't help me, don't post here,
and NO, I WON'T GIVE UP UNTIL WE HAVE A WORKING MIUI ROM.
Status: STUCK ON BOOTANIMATION
You can find more info on MIUI ROM right here: http://en.miui.com/
Changelog:
20140726: Ported from LG / Google Nexus 4
Based on MK4.44 20140726 nightly
20140705 #2: Based on latest 20140705 nightly
20140705: MIUI Patch ROM
20140704 #2: Base updated to "cm-11-20140704-NIGHLTY-falcon"
20140704: Some kernel changes
20140703: First build
Downloads:
20140726: http://www.androidfilehost.com/?fid=23578570567718880
20140705 #2: http://www.androidfilehost.com/?fid=23501681358557999
20140705: http://www.androidfilehost.com/?fid=23501681358557706
20140704 #2: https://www.dropbox.com/s/ws8ioh1kwdelhw6/miui_falcon_4.6.27_20140704_2.zip
20140704: https://www.dropbox.com/s/7blu7jpcvfp7xw1/miui_falcon_4.6.27_20140704.zip
20140703: https://www.dropbox.com/s/vql0c0yp50v4i9p/miui_falcon_4.6.27_20140703.zip
Working:
-
Not working:
-
Instructions:
1. Update recovery
2. Wipe Data / Factory Reset (Format /system if you want)
3. Install the ROM
4. Install GApps
5. Reboot
ROM Review (thanks to TechJunkieReviews):
Credits:
Google / AOSP
@kromuch
dhacker29
Cyanogenmod
MIUI (Xiaomi)
If you help me, your name will be here!
Did you build this, or did you just copy and paste files into a working rom? It'll be hard for a dev to help you if it wasn't built. (to my knowledge at least)
YoshiShaPow said:
Did you build this, or did you just copy and paste files into a working rom? It'll be hard for a dev to help you if it wasn't built. (to my knowledge at least)
Click to expand...
Click to collapse
Yes he ported according to me taking cm as base
And @K3VYNC did u port the kernel?
cant help unless the OP states what steps he / she has taken. we will know what files are missing and what framework needs modification
I working in the port of this from Patch_rom source .----. If any can help send me PM [DEV only and who have knowledge about this.]
EDIT:
did you make changes in bootclaspath in the ramdisk? because you need add directives of MIUI in the ramdisk
Cheers.
TeamMex said:
did you make changes in bootclaspath in the ramdisk? because you need add directives of MIUI in the ramdisk
Click to expand...
Click to collapse
Here is my kernel with shelld in ramdisk, recently I've ported MIUI to Moto G, but it had many software bugs, so, I deleted ROM and now have only ported kernel.
Flash this manually, it's not a flashable ZIP.
Pff we need work a lot xD
Code:
E/qdhwcomposer( 240): hwc_set_primary: display commit fail for 0 dpy!
E/qdhwcomposer( 240): configure: No pipes available to configure fb for dpy 0
E/qdhwcomposer( 240): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Function not implemented
E/qdhwcomposer( 240): hwc_sync: acq_fen_fd_cnt=1 flags=16 fd=16 dpy=0 numHwLayers=2
E/qdoverlay( 240): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Function not implemented
E/qdoverlay( 240): static bool overlay::eek:verlay::displayCommit(const int&, const overlay::utils::Dim&): commit failed
E/qdhwcomposer( 240): hwc_set_primary: display commit fail for 0 dpy!
E/qdhwcomposer( 240): configure: No pipes available to configure fb for dpy 0
E/qdhwcomposer( 240): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Function not implemented
E/qdhwcomposer( 240): hwc_sync: acq_fen_fd_cnt=1 flags=16 fd=16 dpy=0 numHwLayers=2
E/qdoverlay( 240): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Function not implemented
E/qdoverlay( 240): static bool overlay::eek:verlay::displayCommit(const int&,
TeamMex said:
Pff we need work a lot xD
Click to expand...
Click to collapse
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
im waiting for this YOHOO !! MIUI in MOTO G
i hope this will be avaialble on xt1033 variant
kromuch said:
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
Click to expand...
Click to collapse
Your port was from what device ?
it's more EASY make it from source
kromuch said:
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
Click to expand...
Click to collapse
instead of bashing, why dont you post your build or help the guy porting it?
TeamMex said:
Your port was from what device ?
it's more EASY make it from source
Click to expand...
Click to collapse
From the official Nexus 5 (adding to the OP)
Sent from my Moto G using XDA Free mobile app
K3VYNC said:
From the official Nexus 5 (adding to the OP)
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
maybe is better to port it from xiaomi mi2 due to the screen resolution
http://en.miui.com/download-2.html
kromuch said:
Here is my kernel with shelld in ramdisk, recently I've ported MIUI to Moto G, but it had many software bugs, so, I deleted ROM and now have only ported kernel.
Flash this manually, it's not a flashable ZIP.
Click to expand...
Click to collapse
I've added to the ROM
Sent from my Moto G using XDA Free mobile app
TeamMex said:
Your port was from what device ?
Click to expand...
Click to collapse
From Nexus 5 too.
K3VYNC said:
I've added to the ROM, I'm uploading later today
Click to expand...
Click to collapse
Does ROM boot now?
Important! Forgot to say that this kernel is from GPE ROM, so you must flash GPE before flashing MIUI, because Motorola ROM and GPE ROM use different file systems. If anyone give me last Moto-stock kernel (from backup or by another way), I'll add required files to it too. But for Moto-stock kernel must be Moto-stock based port, the same for GPE kernel.
kromuch said:
Yes, from Nexus 5 too.
Does ROM boot now?
Important! Forgot to say that this kernel is from GPE ROM, so you must flash GPE before flashing MIUI, because Motorola ROM and GPE ROM use different file systems.
Click to expand...
Click to collapse
Okay, thanks bro (added to the OP) and no, I couldn't test it.
And yes, I can send you the stock kernel
Sent from my Moto G using XDA Free mobile app
K3VYNC said:
Okay, thanks bro (added to the OP) and no, I couldn't test it, but it's uploading (almost DONE), can you test it?
And yes, I can send you the stock kernel
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
will download it and report...
Edit: download gets canceled at end moment.
The latest build gets an error 509
antarix said:
will download it and report...
Edit: download gets canceled at end moment.
The latest build gets an error 509
Click to expand...
Click to collapse
Try the latest one, tell me if something is changed.
Now I have dev acess to AndroidFileHost! :victory:
Sent from my Moto G using XDA Free mobile app
Cooooll, i watiiiing
Related
Hi Guys....I'm PROUD to release the first BETA of the AOSP rom!)) Let's see the features:
AOSP pure code based on 2.3.7
kernel .35
REVERTED TO AOSP LOCKSCREEN-NEW!!!!!!!!!
Imported power menu from CyanogenMod ( imported only reboot.h library )
USE OF ALL APPS FROM AOSP SOURCES-NEW!!!
Used Mik_os frameworks folder for resolve many bugs so maybe you can find traces of CyanogenMod code
Rooted during compilation
NEED GBAPPS TO FLASH MARKET!!!!(ALSO AOSP NEED THIS AND THIS IS A SURPRISE FOR ME)
FOR OLD BASEBAND!!!!
MODIFIED SURFACEFLINGER.H AND SURFACEFLINGER.CPP TO SUPPORT PERSIST.SYS.USE_16BPP_ALPHA TO GAIN SMOOTHNESS WHEN SCROLLING
OVERALL UI PERFORMANCES GAINED-NEW!!!!!
MODIFIED A BIT EGL DRIVER(@729 OBTAINED 300FPS IN 1ST QUADRANT TEST AND 15 FPS IN 3THD QUADRANT TEST)-NEW!!!!
IMPLEMENTED LATEST FRANCO.KERNEL-NEW!!!!
FIX FOR ELECTRONBEAM ANIMATION THAT LIGHTS UP AFTER UNLOCK(maybe a bug in StageFright replaced with CAF but i need test)-NEW!!!!!
SOME OPTIMIZATIONS CODE!-NEW!!!!!
FIXED HSDPA ICON!(NOW IT SHOWS CORRECTLY)
It works:
Usb
Wifi
adb
audio
sd
gps
camera
shutdown
Usb
GSM-NEW!!
UI-NEW!!
BLUETOOTH-NEW!!
ACCELEROMETHER-NEW!!!!!
doesn't work:
ScreenShots
Headset icon is not showing in statusbar but headset are workin'
AOSP browser still don't work
here the link for the download:http://www.multiupload.com/C1SBJLC0UL
Thanks to
Mik and Andy for help me fixing some bugs
FranciscoFranco for his kernel
drnotor for help me with annoynig NTFS filesystem (looooool)
*******WHAT'S NEXT*************
Workin' on ICS!!!!
Was waiting for a aosp rom, good luck with this.
Thanks for yuA hard work
Sent from LG O¹ • miks cyanogen7.1 with latest testing release kernel v1.1 and v19.3♦• using tapatalk
I really hope you'll make this work, an AOSP rom is just what I would like now.
Good luck with your work!
BTW, if you need some beta testing I think I can help you
Finally a nexus s I CAN AFFORD! Thanks!
Wasn't andy's ROM AOSP too?
ciaox said:
Wasn't andy's ROM AOSP too?
Click to expand...
Click to collapse
Yes it was, but now we don't have another one...
ciaox said:
Wasn't andy's ROM AOSP too?
Click to expand...
Click to collapse
22VIN said:
Yes it was, but now we don't have another one...
Click to expand...
Click to collapse
Yes and no. Andy's rom was based on CAF code (if i remember correctly). CAF code is based on AOSP but it is a different code. Mine rom is based totally on Google code.
Howewer i had an idea......AOSP android 2.3.5 doesn't allow to use 2.2 libraries(i thinked so but it isn't unfrotunately) like CM7.....and i've used these from mik's github...we have a gingerbread update and so 2.3 libraries...i can retrieve these with dsxida's kitchen.....then try to recompile the entire system (even if lg **** 2.3.3 code will doesn't annoying me)but i have the suspect that i must use the new baseband.......see what happens in the next days
any update??????
He has started the thread yesterday only. Let us give him some time to work on it first.
Ok, one question... Is it based on .32 kernel or .35 kernel? Or best someone who ports .38 kernel...
Sent from LGE XDA phone wit Matt's v6.5.7(1.1)
dax4182 said:
Ok, one question... Is it based on .32 kernel or .35 kernel? Or best someone who ports .38 kernel...
Sent from LGE XDA phone wit Matt's v6.5.7(1.1)
Click to expand...
Click to collapse
based on .35 kernel!....now i'm trying to resolve gsm problem (maybe it is a binder problem i've applied some fixes)!
lupohirp said:
based on .35 kernel!....now i'm trying to resolve gsm problem (maybe it is a binder problem i've applied some fixes)!
Click to expand...
Click to collapse
Cool, hope never bricks my phone...
Sent from LGE XDA phone wit Matt's v6.5.7(1.1)
gkarthik16 said:
He has started the thread yesterday only. Let us give him some time to work on it first.
Click to expand...
Click to collapse
Yeah!! But eager to know about his awesome working progress
Sent from my LG-P500 using Tapatalk
grrrrr... NOTHING!!!! it still gave me the same error!(((
Code:
rild
dlopen failed: Cannot load library: link_image[1962]: 2048 could not load neede
d library 'liblgdrm.so' for 'libril-qc-1.so' (reloc_library[1311]: 2048 cannot
locate '_ZNK7android6Parcel16enforceInterfaceERKNS_8String16E'...
)
i've reworked the parcel adding this in PARCEL.CPP
Code:
// LGDRM Section for rild
bool Parcel::enforceInterface(const String16& interface) const
{
return enforceInterface(interface,NULL);
}
and in Parcel.h
Code:
#ifdef _INTERNAL_BINDER_PARCEL_
bool enforceInterface(const String16& interface) const;
#endif
but without success ((((...could anyone help me????i don't think it is only a permission problem.....
Need more patient i think, i saw andy have problem like u... u can read on his topic, before he build last rom and after he delete cm7 rom.. he said something strange with code.. i think u need go and search on another forum.
Have a good luck sir, hope u still doing this project...
Sent from my LG-P500
lupohirp said:
grrrrr... NOTHING!!!! it still gave me the same error!(((
Code:
rild
dlopen failed: Cannot load library: link_image[1962]: 2048 could not load neede
d library 'liblgdrm.so' for 'libril-qc-1.so' (reloc_library[1311]: 2048 cannot
locate '_ZNK7android6Parcel16enforceInterfaceERKNS_8String16E'...
)
i've reworked the parcel adding this in PARCEL.CPP
Code:
// LGDRM Section for rild
bool Parcel::enforceInterface(const String16& interface) const
{
return enforceInterface(interface,NULL);
}
and in Parcel.h
Code:
#ifdef _INTERNAL_BINDER_PARCEL_
bool enforceInterface(const String16& interface) const;
#endif
but without success ((((...could anyone help me????i don't think it is only a permission problem.....
Click to expand...
Click to collapse
Better, you use CAF instead of AOSP: CAF is optimized for MSM devices,
so you have some more luck to get things work.
BTW: RILD cant be used as a compiled thing from android source, LG has
many modifications made to use the baseband. these baseband version
differs in AOSP and CAF/CM7, so better use compiled **** from LG - that should
work.
andy572 said:
Better, you use CAF instead of AOSP: CAF is optimized for MSM devices,
so you have some more luck to get things work.
BTW: RILD cant be used as a compiled thing from android source, LG has
many modifications made to use the baseband. these baseband version
differs in AOSP and CAF/CM7, so better use compiled **** from LG - that should
work.
Click to expand...
Click to collapse
infact i'm downloading the coeduarora sources and try their rild libraries ...BTW i've maded some modifcations to opensource gralloc (set 16 bit per pixel instead of 32 bit in framebuffer.cpp to gain more smoothness ) but i dunno how to compile it.....i've only to copy the libgralloc folder in device/lge/thunderg and then compile or i must call somewhere in the device folder????sorry for the dumb question but i'm very new to android ((
lupohirp said:
infact i'm downloading the coeduarora sources and try their rild libraries ...BTW i've maded some modifcations to opensource gralloc (set 16 bit per pixel instead of 32 bit in framebuffer.cpp to gain more smoothness ) but i dunno how to compile it.....i've only to copy the libgralloc folder in device/lge/thunderg and then compile or i must call somewhere in the device folder????sorry for the dumb question but i'm very new to android ((
Click to expand...
Click to collapse
I'm not even sure P500 supports 32-bits framebuffer, not even my x5 does so that was a good call.
franciscofranco said:
I'm not even sure P500 supports 32-bits framebuffer, not even my x5 does so that was a good call.
Click to expand...
Click to collapse
infact i use the opensource libgralloc.....and i founded that it use a 32-bit per pixel (think was the reason also to the strange UI behaviour that i have) i set 16 bit and see...also made some changes to framework....now i'm going to recompile to see what happens...i've copied only libgralloc folder in device
Welcome to the Android Open Source Project!Android is an open-source software stack for a wide range of mobile devices and a corresponding open-source project led by Google. Here you can find the information and source code you need to learn more about the Android platform. From there you can create custom variants of the Android software stack, port devices and accessories to the Android platform, and ensure your devices are compatible with the Android compatibility definition.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Downloads:
-03302015: click here.
-04102015: click here.
-Gapps: use compatible one with 5.1.
Works:
-Wifi.
-GPS.
-Camera.
-Video Camera.
-Screen Shots.
-Flashlight.
-RIL (calls, data, sms, USSD Code, Contact and Dialer).
-Audio (Playback and recording).
-Video (Playback and recording),
-Recent apps.
-Charging is fixed, check them when phone is locked .
-Now all apps are compatible.
-All related bugs will be set under known issues.
Known Issues:
Video recording need to be fixed.
NFC: install NFC Destroyer to remove it if not used.
Click to expand...
Click to collapse
Installation
Make a backup!.
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to stock 4.2 first.
Install ClockworkMod recovery with SELinux support (.tar) (.zip). Older CWM will result in a "status 7" error.
Reboot into recovery.
Wipe data if coming from stock or other ROMs (You may get a "status 7" error if you fail to wipe.).
Install the ROM.
Optionally install the Google Apps Addon.
Click to expand...
Click to collapse
Installation Guide of i9105:
Take same rom.
extract updater-script in meta-inf and rename all s2vep to s2ve.
remove old updater-script and replace edited one.
Flash the rom then NFC Destroyer, enjoy.
Click to expand...
Click to collapse
How To Install Root on 5.1:
Download UPDATE-SuperSU-v2.46.zip and copy to sdcard from attacched file.
Reboot into TWRP Recovery.
Click on Install.
Choose UPDATE-SuperSU-v2.46.zip.
Swipe to start flashing.
Reboot and install SuperSu's Chainfire application and run the script to
complete installation.
Click to expand...
Click to collapse
Changes Log:
03/29/2015:
-Redownload AOSP 5.1 R3 source.
-Rebase the source with new changes for AOSP.
03/30/2015:
-Everything works fine.
-This rom will be updated always.
04/09/2015
-Apply new set of patches.
-Correct some flags on device tree.
-Recompile kernel with Nebula.
04/10/2015
-Recent apps: fixed.
-Data: fixed DON'T TELL ME ANYMORE ABOUT "DATA NOT WORKING FOR ME",
SEE MY ATTACCHED IMAGE OR FLASH COOL/NEBULA TO FIX IT BY YOURSELF.
Click to expand...
Click to collapse
Thanks
- The CyanogenMod team for some of the compatibility patches used in this ROM
Contributors
@haky86
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Snapshot
Created 2015-03-22
Last Updated 2015-03-30
reserved
Link ?
@haky 86: why am I listed as a guy who made CM12?
LuK1337 said:
@haky 86: why am I listed as a guy who made CM12?
Click to expand...
Click to collapse
probably it's my fault..i will correct
naskodeuces said:
Link ?
Click to expand...
Click to collapse
Not yet.
Reserved2: I just rename the flashable after all this screenshots to reinstall with gapps and root, it's stuck after google animation boot and the only thing is appear is power off menu, consider i am recompiling again
Reserved3: uploaded rom, i will try to fix camera
haky 86 said:
Reserved2: I just rename the flashable after all this screenshots to reinstall with gapps and root, it's stuck after google animation boot and the only thing is appear is power off menu, consider i am recompiling again
Reserved3: uploaded rom, i will try to fix camera
Click to expand...
Click to collapse
Good work! :good:
Message application FC trying to open a sms.
Very fast apart dialer app!
I fetch same problem on omni about dialer
Sent from my GT-I9105P using XDA Free mobile app
haky 86 said:
I fetch same problem on omni about dialer
Sent from my GT-I9105P using XDA Free mobile app
Click to expand...
Click to collapse
Any news Hakam, about fixes?
beegee said:
Any news Hakam, about fixes?
Click to expand...
Click to collapse
I am recompiling againg, after redownload source, and device tree with new changes:angel:
New build is out and i am uploading it.
haky 86 said:
New build is out and i am uploading it.
Click to expand...
Click to collapse
What is the change log
No signal on carrier locked phone :crying:
Sheldd said:
No signal on carrier locked phone :crying:
Click to expand...
Click to collapse
Thanks for telling that
If u flash it, i cant have also data, im carrier locked @haky86 contact andixml i think it is related to SEPolicy.
OK guys I will contact andixml, for hangouts, it's not device tree bug i think its related to gapps, at leat I will test with i9082 device tree renamed to i9105p and see .
Edited: data is work for me!
Sheldd said:
No signal on carrier locked phone :crying:
Click to expand...
Click to collapse
Thanks for feedback the issue, I will recompile a new build based on i9082 renamed to i9105, i am sure will got everything worked or I will f*** myself. after testing the new firmware
haky 86 said:
Thanks for feedback the issue, I will recompile a new build based on i9082 renamed to i9105, i am sure will got everything worked or I will f*** myself. after testing the new firmware
Click to expand...
Click to collapse
No need to, i already tested it.
Same as other ones
beegee said:
No need to, i already tested it.
Same as other ones
Click to expand...
Click to collapse
OK bro, for the new build of aosp I will stard building in the evening based on i9082 renamed to i9105p, i hope to got everything worked
haky 86 said:
Thanks for feedback the issue, I will recompile a new build based on i9082 renamed to i9105, i am sure will got everything worked or I will f*** myself. after testing the new firmware
Click to expand...
Click to collapse
Ok, thanks for that :angel:
Complete Kernel Source Code is essential for building rom from scratch
what lenovo did it give us incomplete Code missing the important files and directories and hide the essential part
Lenovo should release kernel source in full, so we can look after our self
Kernel development doesn't take place unless we get the device's schematics and its corresponding defconfig.
Lenovo has hidden the caf tag inside the firmware. there is matching qcom caf kernel tag for the same chipset. But without the schematics of the device, we couldn't proceed in developing
until now the official source is incomplete
but some developers trying to fill the gaps from similar devices you can find these builds on github
here is the last source kernel from lenovo and github
Downloads:
kerenel source from github by Flour_Mo :
here
kerenel source from github by ramsudharsan updated 20/8/2015 :
Here
kerenel source from Lenovo updated 7/8/2015:
Here
XDA:DevDB Information
Towards a Complete Kernel Source Code For Lenovo A6000 / Plus, ROM for the Android General
Contributors
ED300
ROM OS Version: 5.1.1. Lollipop
Version Information
Status: Testing
Created 2015-08-24
Last Updated 2015-08-24
When u develop your own kernel?
sourav8434 said:
When u develop your own kernel?
Click to expand...
Click to collapse
when i have a complete source kernel
what are you making
For which rom you are working now and when u will release kernel for lenovo a6000
check this out please
check this link please if it is complete or not
xttp://lenovo-forums.ru/topic/11326-lenovo-a6000-%D0%B8%D1%81%D1%85%D0%BE%D0%B4%D0%BD%D1%8B%D0%B9-%D0%BA%D0%BE%D0%B4-%D1%8F%D0%B4%D1%80%D0%B0/?hl=%2Ba6000+%2Bplus
change x to h
SIMBIOS said:
check this link please if it is complete or not
xttp://lenovo-forums.ru/topic/11326-lenovo-a6000-%D0%B8%D1%81%D1%85%D0%BE%D0%B4%D0%BD%D1%8B%D0%B9-%D0%BA%D0%BE%D0%B4-%D1%8F%D0%B4%D1%80%D0%B0/?hl=%2Ba6000+%2Bplus
change x to h
Click to expand...
Click to collapse
this is the same incomplete lenovo source
sourav8434 said:
For which rom you are working now and when u will release kernel for lenovo a6000
Click to expand...
Click to collapse
don't worry good news coming in the way
what news
ED300 said:
don't worry good news coming in the way
Click to expand...
Click to collapse
Whats that news ed3000
bad news
ED300 said:
don't worry good news coming in the way
Click to expand...
Click to collapse
hey i just checked lenovo site now lollipop update is in september
whats the good news?
SIMBIOS said:
hey i just checked lenovo site now lollipop update is in september
whats the good news?
Click to expand...
Click to collapse
i can't confirm any thing now ,
but i think the coming days we will make progress to solve sim bug completely on CM12.1
missing things
Hi,
I find following things missing from stock kernel
1. whole kernel directory all together
2. Def-config (altough i managed to extract it from boot.img)
Do you what are other things that are missing?
I'm able to compile the kernel with some fixes from cm kernel, but now able to generate the dtb file. Any help will be appreciated.
Thanks
Chhapil
yay
ED300 said:
i can't confirm any thing now ,
but i think the coming days we will make progress to solve sim bug completely on CM12.1
Click to expand...
Click to collapse
good luck hope you fix it praying for u
Hello how can i fix my phone lenovo A6000 it always pop up please input puk code.. How can i remove it? Thanks
Penggot said:
Hello how can i fix my phone lenovo A6000 it always pop up please input puk code.. How can i remove it? Thanks
Click to expand...
Click to collapse
i think the problem on the sim try different sim and see what happen
chhapil said:
Hi,
I find following things missing from stock kernel
1. whole kernel directory all together
2. Def-config (altough i managed to extract it from boot.img)
Do you what are other things that are missing?
I'm able to compile the kernel with some fixes from cm kernel, but now able to generate the dtb file. Any help will be appreciated.
Thanks
Chhapil
Click to expand...
Click to collapse
good job chhapil
i gave links to kernel source from github it should be completed
you will find also at github the source for cynogenmod 12.1 if you want compile it
Here is the latest update from my side.
I'm able to create zimage from kernel, dtb from source. But the kernel fails to boot.
If I flash my kernel the phone restarts with blank screen and it mounts all the partitions when connected to pc.
I'm not very sure what's going wrong.
Sent from my GT-I9100 using XDA Free mobile app
chhapil said:
Here is the latest update from my side.
I'm able to create zimage from kernel, dtb from source. But the kernel fails to boot.
If I flash my kernel the phone restarts with blank screen and it mounts all the partitions when connected to pc.
I'm not very sure what's going wrong.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
try this link :
https://github.com/Silentlys/Cyanogenmod_device_lenovo_Kraft_T/tree/cm12.1
copy from kernel folder to kernel source and compile
you will find also zimage ready
kernel for lenovo a6000
chhapil said:
Here is the latest update from my side.
I'm able to create zimage from kernel, dtb from source. But the kernel fails to boot.
If I flash my kernel the phone restarts with blank screen and it mounts all the partitions when connected to pc.
I'm not very sure what's going wrong.
Sent from my GT-I9100 using XDA Free mobile app[/QUOTE.
Hey. Chhapil. When will you release kernel for lenovo a6000/plus?
Have u made if you made then post please
We will be thankful
Click to expand...
Click to collapse
There is no point releasing non working kernel.
Let's wait till ED300 posts a working build or Lenovo themselves.
Sent from my GT-I9100 using XDA Free mobile app
kernel boot issue
Hi,
Here is the issue i'm facing.
I created a new image from the KK stock kernel + the missing parts , repacked it the boot.img from the stock rom.
When i do
fastboot boot new-boot.img
the phone reboots and mounts the system partition and couple of other internal partitions with no display.
Do you know these symptoms?
Any Idea what could be going wrong here?
On the other note,
the LP source code compile good without any issues at all, but I'm using stock KK so there is NO room for to make tries with it.
ROM DEPRECATED, USE LAST CM11 HERE
ROM DEPRECATED, USE LAST CM11 HERE
USE ONLY LASTEST BUILD
I forgot the rom name but there's a kitkat rom with no screen flickering issue by niropa (on lollipo bootloader). u can contact with niropa to solve screen flickering issue.
Yes,was in a wrong place, i have contacted a moderator, now is in android development.
Ok , i think cm11 its the most stable tree from cm team , i like KK because its more ligth weigth , i dont know why the developers wonma make roms unstable and buggies hehe , can u add a custom features? Like another toolchain? (Linaro , Uber) or new features from kernel? Like more i/o (zen ) , gpu OC or cpu OC?...
Anyway , Thank U its run great
Enviado desde mi Moto G mediante Tapatalk
STR4NG3R-GUY said:
Ok , i think cm11 its the most stable tree from cm team , i like KK because its more ligth weigth , i dont know why the developers wonma make roms unstable and buggies hehe , can u add a custom features? Like another toolchain? (Linaro , Uber) or new features from kernel? Like more i/o (zen ) , gpu OC or cpu OC?...
Anyway , Thank U its run great
Enviado desde mi Moto G mediante Tapatalk
Click to expand...
Click to collapse
unfortunately I am only at the beginning, I'm learning slowly how to create rom from source code, for the moment I do not know to create kernels with overcloclock or similar. I'm only 15 years old, and this is the second ROM in total which I compile
SLATE21&MOTOG said:
this rom works with all bootloader, kitkat and lollipop, but with the lollipop one you will get screen flickering. If anyone knows how I can do a build with no screen flickering can contact me in pm.
Click to expand...
Click to collapse
See PACMan builds with overkill kernel by niropa. Just search in that thread and you'll find many ROMs like CarbonKK or PA, which are made to work on LP bootloader
Will this work on msim variant also? I read you mentioned xt1032 but still if you know..
It might work, but has been tested only on xt1032 aka falcon.
tested on XT1033, very stable ROM, smooth ROM ever :fingers-crossed::fingers-crossed:
Stock cm11 kernel or something else is there? I can see "overkill kernel" that reminds me really good things
Rocketval said:
Stock cm11 kernel or something else is there? I can see "overkill kernel" that reminds me really good things
Click to expand...
Click to collapse
Yes, I have used Overkill kernel that @Niropa has used in his Pac-man rom build, with the hope of fix the screen flickering, but the problem remain. This is aniway a good and stable kernel. For more information see: https://github.com/ReaperXL2/Overkill_V4_extended/tree/cm-11.0
SLATE21&MOTOG said:
Yes, I have used Overkill kernel that @Niropa has used in his Pac-man rom build, with the hope of fix the screen flickering, but the problem remain. This is aniway a good and stable kernel. For more information see: https://github.com/ReaperXL2/Overkill_V4_extended/tree/cm-11.0
Click to expand...
Click to collapse
But are kernel sources updated? Or using it cause some incompatility such as hotspot, bt or something else?
All work fine, bluetooth and hotspot work. I have tested it, the only warnings are 3:
-Do not active kernel samepage merging, you will have problem in camera
-install gapps only after the first reboot of the rom
-If you use whatsapp install it before switching to ART (in developer setting, for better performance select ART)
There aren't particular bugs
SLATE21&MOTOG said:
All work fine, bluetooth and hotspot work. I have tested it, the only warnings are 3:
-Do not active kernel samepage merging, you will have problem in camera
-install gapps only after the first reboot of the rom
-If you use whatsapp install it before switching to ART (in developer setting, for better performance select ART)
There aren't particular bugs
Click to expand...
Click to collapse
Why gapps only on second boot?
ale467 said:
Why gapps only on second boot?
Click to expand...
Click to collapse
Because if you install the rom and after the gapps and you reboot, the setup wizard crash. I have tryed it
https://www.youtube.com/watch?v=YFATFIufW7Q&feature=youtu.be
This is a small video demonstration of the rom, 60 second.
SLATE21&MOTOG said:
Yes, I have used Overkill kernel that @Niropa has used in his Pac-man rom build, with the hope of fix the screen flickering, but the problem remain. This is aniway a good and stable kernel. For more information see: https://github.com/ReaperXL2/Overkill_V4_extended/tree/cm-11.0
Click to expand...
Click to collapse
Check out xperience kernel to get rid of screen flickering
Niropa said:
Check out xperience kernel to get rid of screen flickering
Click to expand...
Click to collapse
could you give me the kernel link on github ?
SLATE21&MOTOG said:
could you give me the kernel link on github ?
Click to expand...
Click to collapse
I don't have the link I haven't built for the moto g in ages, just go to the xperience thread, their is only 1 kernel by teamex called xperience
Note: I am not in any way a developer of the Boeffla-Kernel. I asked the developer, @Lord Boeffla, if it would be OK to post a modified version of his kernel on this forum. He agreed but indicated that he will not be providing support for his kernel on the SM-G900V and, as per his FAQ, he is not willing to take on any new Samsung models. Please do not ask him for help or request that he officially support the Verizon model.
Disclaimer: Install this kernel at your own risk. Neither I nor the kernel developers take any responsibility for any damage done by flashing or running this kernel and no support can be offered.
Requirements
A developer aboot
Custom recovery (I use TWRP)
Either a Samsung Stock Lollipop or CM13 based ROM
Root (to run the Boeffla-Config app)
Optional: FlashFire
Please make a full nandroid backup before flashing anything. If you're already using a custom kernel, use the Cleaner Script below. If you're using stock Samsung, make sure it is the latest version of Lollipop. Use custom recovery or FlashFire to flash. Afterwards, install the latest Boeffla-Config app.
Downloads
If coming from a different custom kernel, use this cleaner script before flashing the kernel:
Boeffla_Cleaner_Script_SM-G900V_V1.zip
For Samsung Stock Lollipop based ROMs:
boeffla-kernel-1.0-test-Samsung-g900v.recovery.zip
For Cyanogenmod 13 based ROMs:
boeffla-kernel-1.0-test-CM13.0-g900v.recovery.zip
For Resurrection Remix ROMs:
As of late komarov27 has been supporting a Resurrection Remix Boeffla Kernel compatible with the kltevzw in the comments section of the main S5 Resurrection Remix thread ( here for instance). Please see the thread for the latest version.
Regardless of which Boeffla kernel you flashed, install the latest Boeffla-Config app for tweaking goodness:
Boeffla-Config
Known problems
Some custom CM13 ROMS may produce stalls or boot-loops during bootup with the Boeffla Kernel, especially after cleaning the cache and/or Art/Dalvik cache. The ResurrectionRemix version of the Boeffla Kernel may fix the problem but not every CM13 ROM should be expected to work. Always make a full nandroid backup ahead of time.
Be careful with xposed as some have reported issues with modules that alter kernel options.
The original Boeffla Kernel thread for Samsung stock can be found here.
The original Boeffla Kernel thread for CM can be found here.
The official Boeffla Kernel site can be found here.
A special thanks to @Lord Boeffla for the kernel.
Reserved...
Cleaned cache and dalvik with RR and Boeffla and dont bootlooped... And i am using xposed, not notice nothing wrong...
Nsane457 said:
The original Samsung Boeffla Kernel thread can be found here.
Click to expand...
Click to collapse
Maybe this link are more accurate?
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062078
TioCareca said:
Cleaned cache and dalvik with RR and Boeffla and dont bootlooped... And i am using exposed, not notice nothing wrong...
Click to expand...
Click to collapse
Good to know. It always stalls for me on boot with RR if I wipe the dalvik cache. I expect many people won't have any trouble with xposed but it is still not advised.
TioCareca said:
Maybe this link are more accurate?
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062078
Click to expand...
Click to collapse
The link I gave was for the Samsung stock version but I've added this one for the CM version. Thanks.
Yes i see your point, the warnings are made...
The xposed problems are caused by modules that change kernel options, not xposed itself so is pretty safe to use with the right modules...
Maybe this for the stock version? Your link is for S3....
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062073
TioCareca said:
Yes i see your point, the warnings are made...
The xposed problems are caused by modules that change kernel options, not xposed itself so is pretty safe to use with the right modules...
Click to expand...
Click to collapse
OK. I'll adjust the warning.
TioCareca said:
Maybe this for the stock version? Your link is for S3....
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062073
Click to expand...
Click to collapse
Yes. Sorry about that. The link is updated.
No problem... Just trying to help... I will make some experiments with the kernel source code...
TioCareca said:
No problem... Just trying to help... I will make some experiments with the kernel source code...
Click to expand...
Click to collapse
That would be fine. :good: I have some experience with cross-compiling but none with Android. Sadly, the script used for building the Boeffla Kernel apparently didn't work with python3, gcc-5.*, or the version of perl I was using. I just got tired of installing different versions of my libraries and adjusting defaults.
I just updated the thread with a patched version of Boeffla-Kernel that works with ResurrectionRemix ROM, thanks to @j1gga84. It finally fixes the bootloop/stall problem I've been having.
Link to original post
Nsane457 said:
I just updated the thread with a patched version of Boeffla-Kernel that works with ResurrectionRemix ROM, thanks to @j1gga84. It finally fixes the bootloop/stall problem I've been having.
Link to original post
Click to expand...
Click to collapse
If BETA20 was RR fix what did BETA21 change?
Does this kernel support CPU oc?
Sent from my SM-G900V using XDA-Developers mobile app
jordash25 said:
If BETA20 was RR fix what did BETA21 change?
Click to expand...
Click to collapse
From here:
CM13.0 -- Version 3.0-beta21
12.04.2016
Update: Updated with latest official CM kernel commits as of 12.04.16, 8am CET
Update: Ramdisk of official CM13.0 build of 12.04.16
Click to expand...
Click to collapse
thrgk said:
Does this kernel support CPU oc?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. Overclocking and underclocking. See here for config info.
Beoffla Kernel for Ressurection Remix ROM updated to boeffla-kernel-3.0-beta22-RR-kltevzw.zip.
Nsane457 said:
If coming from a different custom kernel, use this cleaner script before flashing the kernel:
Boeffla_Cleaner_Script_SM-G900V_V1.zip
For Samsung Stock Lollipop based ROMs:
Stable: boeffla-kernel-1.4-Samsung-g900v.recovery.zip
Click to expand...
Click to collapse
Hi there! thanks for the port, it looks amazing!
Quick question. I have installed the two files I quoted, and everything looks like is working fine (System, Xposed, etc). However, when I open the Terminal it tells me this:
Code:
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "/system/bin/sh"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "getprop"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "id"; caused by library "libNimsWrap.so" not found
[email protected]:/ $
I tried googling it and couldn't find a solution, but I know for sure it is the custom Kernel because I tried troubleshooting it and it only shows up with the custom Kernel (not even related to Xposed). Does this happen to you too?
Thanks again!
rauleeros said:
Hi there! thanks for the port, it looks amazing!
Quick question. I have installed the two files I quoted, and everything looks like is working fine (System, Xposed, etc). However, when I open the Terminal it tells me this:
Code:
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "/system/bin/sh"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "getprop"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "id"; caused by library "libNimsWrap.so" not found
[email protected]:/ $
I tried googling it and couldn't find a solution, but I know for sure it is the custom Kernel because I tried troubleshooting it and it only shows up with the custom Kernel (not even related to Xposed). Does this happen to you too?
Thanks again!
Click to expand...
Click to collapse
It mentions your issue on this thread.
I'll try to install and troubleshoot it tonight.
Nsane457 said:
It mentions your issue on this thread.
I'll try to install and troubleshoot it tonight.
Click to expand...
Click to collapse
You are amazing!
P.S. I followed what the said: move the libs that it asks for (libNimsWrap.so & then libcnefeatureconfig.so) to the /system/lib/ folder and change the permissions. Open the terminal.... And gone!
rauleeros said:
You are amazing!
P.S. I followed what the said: move the libs that it asks for (libNimsWrap.so & then libcnefeatureconfig.so) to the /system/lib/ folder and change the permissions. Open the terminal.... And gone!
Click to expand...
Click to collapse
Yeah. It seems to be caused by a line in the "init.environ.rc" script in the boot ramdisk. I'll look into fixing it later. For now the workaround is fine and either way it should be harmless.
Bootlooped on 5.0 AllianceRom Xposed. Don't have much information to give you besides it doesn't work. Unlocked the retail bootloader.
Dashaquavius said:
Bootlooped on 5.0 AllianceRom Xposed. Don't have much information to give you besides it doesn't work. Unlocked the retail bootloader.
Click to expand...
Click to collapse
Its for 6.0 roms only...