Hello everyone,
I'm excited to announce my kernel for the P6000 Pro, whooohooo! It is basically stock with 1.5 Ghz for now but my tester @Nikolaosf is currently testing the DoubleTap2Wake build, so this will probably come soon as well to this device.
The usual disclaimer applies:
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 kernel
* before flashing it! YOU are choosing to make these modifications.breaks
*/
Changelog:
Code:
0.7:
* 1,5 GHz Overclocking!
Source: https://github.com/visi0nary/android_kernel_elephone_p8000
How to install:
Either use rashr or unlock fastboot and follow these steps:
1. Download kernel
2. Go to download directory.
3. Reboot device into fastboot mode.
4. Type "fastboot flash boot visi0narys_kernel_p6000_pro_vx.x.img"
Props fly out to to:
* carliv, I learned a lot from you!
* Eugen, for the Skype support and for being an awesome guy!
* showp, thanks for DT2W!
* @Nikolaosf for testing over and over again!
* everyone else I forgot
Q&A:
Can I still use 1.3 GHz as maximum frequency?
-> Yep, just limit it manually. A convenient way to do this is the app Trickster Mod for example.
I'm excited to get feedback so please report back if you find any issues but please let me also know if everything works
Please note that I don't own the device and am building blindly, so leave feedback if something is broken! The kernel is built from P8000 sources and I'd like to port my work to the P6000 Pro.
It is working perfectly the oc 0.7v...thanks thanks thanksss!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Testing DT2W
Nice one @BlueFlame4.
It would be great to see DoubleTap2Wake. The P6000 Pro also has the bug where the capacitive buttons will wake the phone (They don't wake the phone when it's been freshly booted, only after a certain period of up time). I believe you addressed that on the P8000 kernel?
Here is my test on my P6000 Pro running stock 5.1 ROM:
Trickster MOD reports max frequency of 1495MHz
AnTUTu Benchmark 5.7.1 64 bit
Stock kernel:
36157
35860
visi0nary's 0.7 kernel:
37452
37152
I will report back any other observations.
Try geekbench too
Nikolaosf said:
Try geekbench too
Click to expand...
Click to collapse
No need to duplicate your results everything is working OK and your results look good
How is your testing of DT2W going?
Martin
Just wanted to see if the dif of before and after is such as small like mine..
.
Not yet DT2W... Blue is working on cm at most this time
my p8000 port to p6000pro
http://forum.xda-developers.com/android/development/rom-18-11-eragon-v1-0-p6000-pro-android-t3251881
@BlueFlame4, There is commit 66de890a92e172155c54e860896e6fe03761a5da in visi0nary kernel repo on github.
Merge pull request #1 from Netmatrix/patch-1
Update gt9xx_driver.c to enable touch in recovery!
Click to expand...
Click to collapse
https://github.com/visi0nary/androi...mmit/66de890a92e172155c54e860896e6fe03761a5da
It's essential, because it enable touch in recovery mode, thus it would be possble to have working TWRP on P6000 Pro.
Can I kindly ask you to build a fresh version of visi0nary's kernel for P6000 Pro with this commit applied.
Thanks in advance.
lion567 said:
@BlueFlame4, There is commit 66de890a92e172155c54e860896e6fe03761a5da in visi0nary kernel repo on github.
https://github.com/visi0nary/androi...mmit/66de890a92e172155c54e860896e6fe03761a5da
It's essential, because it enable touch in recovery mode, thus it would be possble to have working TWRP on P6000 Pro.
Can I kindly ask you to build a fresh version of visi0nary's kernel for P6000 Pro with this commit applied.
Thanks in advance.
Click to expand...
Click to collapse
Don't have time for these things now but the defconfig is online so feel free to build it The OC is only visual btw so this kernel is basically useless now. Will add DT2W one day though BTW I am visi0nary on GitHub so I know what commit you're talking about, haha.
BlueFlame4 said:
Don't have time for these things now but the defconfig is online so feel free to build it The OC is only visual btw so this kernel is basically useless now. Will add DT2W one day though BTW I am visi0nary on GitHub so I know what commit you're talking about, haha.
Click to expand...
Click to collapse
Sorry for a newbie question, but what is the different between a P6000 Pro and P8000 boot.img file?
When you say 'build' - is it unpacking the P8000 boot.img you created, and repack for P6000 Pro? Or does it need to be compiled from the Github source for P6000 Pro?
blahmartinblah said:
Sorry for a newbie question, but what is the different between a P6000 Pro and P8000 boot.img file?
When you say 'build' - is it unpacking the P8000 boot.img you created, and repack for P6000 Pro? Or does it need to be compiled from the Github source for P6000 Pro?
Click to expand...
Click to collapse
No worries, asking questions is the best way to learn
The kernel has to be compiled again as the configs differ because of different hardware. Afterwards it is repacked into its own ramdisk, yep.
BlueFlame4 said:
No worries, asking questions is the best way to learn
Click to expand...
Click to collapse
:good:
Can you provide me with correct commands sequence for compiling kernel for P6000 Pro after I cloned your repo with git?
It seems, that
Code:
lunch k01ts_a
make bootimage
shouldn't work
lion567 said:
:good:
Can you provide me with correct commands sequence for compiling kernel for P6000 Pro after I cloned your repo with git?
It seems, that
Code:
lunch k01ts_a
make bootimage
shouldn't work
Click to expand...
Click to collapse
Well, I build the kernel standalone for now so without importing it into CMs build chain.
Code:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- xxxxxx_defconfig
Sets up your kernel config.
Code:
make -jX
Compiles with X cores. Defconfigs can be found unter arch/arm64/configs and the resulting image is under arch/arm64/boot (it's the dtb one). If it doesn't work right away you gotta set $ARCH to arm64.
Depending on what toolchain you use you have to add it to your $PATH.
Happy hacking!
Thanks @BlueFlame4
I was trying to get that to build last night too. Appreciate your help! I will try again later with thus new knowledge.
Martin
BlueFlame4 said:
Well, I build the kernel standalone for now so without importing it into CMs build chain.
Code:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- xxxxxx_defconfig
Sets up your kernel config.
Code:
make -jX
Compiles with X cores. Defconfigs can be found unter arch/arm64/configs and the resulting image is under arch/arm64/boot (it's the dtb one). If it doesn't work right away you gotta set $ARCH to arm64.
Depending on what toolchain you use you have to add it to your $PATH.
Happy hacking!
Click to expand...
Click to collapse
Thanks a lot!
k01ts_a_defconfig is correct defconfig for building P6000 Pro kernel isn't it?
lion567 said:
Thanks a lot!
k01ts_a_defconfig is correct defconfig for building P6000 Pro kernel isn't it?
Click to expand...
Click to collapse
Yes if I recall correctly. But you can easily find it out - e.g. in build.prop or just from the file name from original ROMS.
Thank you!
BlueFlame4 said:
Yes if I recall correctly. But you can easily find it out - e.g. in build.prop or just from the file name from original ROMS.
Click to expand...
Click to collapse
Yes P6000 Pro has k01ts_a name in stock build.prop
Code:
ro.product.device=k01ts_a
but there are several defconfig files with similar names, so I was in doubt.
Finally I've managed to buid fresh kernel for P6000 Pro from your repo succesfully! Thank you very much!
I've repacked PhilZ 6 image (which I've already used with hardware buttons only) with this fresh kernel and it became fully touchable!!! :good:
And AromaFM filemanager for recovery also works fine with touch now!
lion567 said:
Yes P6000 Pro has k01ts_a name in stock build.prop
Code:
ro.product.device=k01ts_a
but there are several defconfig files with similar names, so I was in doubt.
Finally I've managed to buid fresh kernel for P6000 Pro from your repo succesfully! Thank you very much!
I've repacked PhilZ 6 image (which I've already used with hardware buttons only) with this fresh kernel and it became fully touchable!!! :good:
And AromaFM filemanager for recovery also works fine with touch now!
Click to expand...
Click to collapse
can you please share your kernel with this touch recovery?
lion567 said:
Yes P6000 Pro has k01ts_a name in stock build.prop
Code:
ro.product.device=k01ts_a
but there are several defconfig files with similar names, so I was in doubt.
Finally I've managed to buid fresh kernel for P6000 Pro from your repo succesfully! Thank you very much!
I've repacked PhilZ 6 image (which I've already used with hardware buttons only) with this fresh kernel and it became fully touchable!!! :good:
And AromaFM filemanager for recovery also works fine with touch now!
Click to expand...
Click to collapse
\o/ Yay! Congrats!
jozsi76 said:
can you please share your kernel with this touch recovery?
Click to expand...
Click to collapse
Surely, but in another thread. Look here http://forum.xda-developers.com/showpost.php?p=64038183&postcount=52
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
I AM NOT RESPONSIBLE FOR BRICKED DEVICES AND ETC ****
Code:
* Various fixes, improvements and optimizatios (look @ github)
* Compiled with gcc4.7 toolchain (linaro)
* Updated to [B]3.4.84[/B]
* Default clocks: [B]1188 Mhz[/B]
* Dual Recovery [B]CWM+TWRP[/B]
* SE-Linux Support
* Clean and Simple with No ****
* Fixed Storage on kitkat (Credit @siankatabg)
* New build as soon as Original Linux tree updates
DOWNLOAD JB
Code:
[url]http://www.mediafire.com/download/usrs539q5pas6r5/Civic-O2-2.2-JB.zip[/url]
DOWNLOAD KITKAT
Code:
[URL]http://www.mediafire.com/download/d1m1anbo0lcjso4/Civic-O2-2.2-kk.zip[/URL]
HOW TO USE DUAL RECOVERY?
Code:
LIGHT WILL GLOW AT THE START OF PHONE
[B]
PINK LIGHT -->[COLOR="DarkRed"]VOLUME DOWN[/COLOR] --> TWRP
RED LIGHT -->[COLOR="DarkRed"]VOLUME DOWN[/COLOR] --> CWM[/B]
Note that first pink light will glow and then red , so if you want to boot into
CWM ,you will have to wait
HOW TO DEAL WITH KITKAT STORAGE?
Just Type in Terminal emulator these commands
Code:
su
cd /mnt/media_rw/sdcard0
mv !(0|legacy|obb) 0
CHANGELOG
Version 2.2
* Some fixes regarding SE-linux
* SE-Linux to permissive mode
* Updated to 3.4.84 latest
* Changed Prima flag should fix some WiFi disconnections
* Fixed storage on kitkat (Thanks to siankatabg)
* OC upto 1.2
Version 2.0
* Various fixes, improvements and optimizatios (look @ github)
* Compiled with gcc4.7 toolchain (linaro)
* Updated to 3.4.83
* Default clocks: 1026 Mhz
* Dual Recovery CWM+TWRP
* SE-Linux Support
GITHUB
Sources:https://github.com/aniketroxx/civic-sa77
Ramdisk:https://github.com/aniketroxx/ramdisk-dual-Recovery
Compiler: Linaro GCC 4.7 ToolChain
Branch: Android 4.2.2
Kernel Version: 3.4.84
Thanks
rachit, varun.chitre15, Doomlord, Faux123, killerkink,vishal_android freak
Click to expand...
Click to collapse
#Big Thanks to Raj Joshi for testing my beta builds everytime
If anybody wants to use my kernel ramdisk simply mention the sources
Click to expand...
Click to collapse
Version Information
Status: Stable
Current Stable Version: 2.2
Last Updated 2014-25-3
This is based from stock without stripped anything??
Yes its based on stock, no oc
Sent from my C2104 using xda app-developers app
What is the Difference between this and Phantom Kernel V3 ? -,-
Both are Stock and Both got touch imporved and Both got CWM
I hope you add some improvements in the next versions
Sparksys said:
What is the Difference between this and Phantom Kernel V3 ? -,-
Both are Stock and Both got touch imporved and Both got CWM
I hope you add some improvements in the next versions
Click to expand...
Click to collapse
Try it bro once:good:
Good Work
aniketroxx said:
Well i am just beginner in the kernel development section and this is my first kernel .I named it "civic" kernel.I made this kernel from scratch and compiled from stock source.Thanks to Shivam Kucchal for his help and encouragement
"Whats in kernel"
Instructions-
1- Flash boot.img through fastboot mode.
2- Flash modules.zip through recovery.
Download the boot.img from below:-
https://www.dropbox.com/s/wt6n6dam6tq24y8/boot.img
Download Modules:-
https://www.dropbox.com/s/3cvcu9umddlfprw/Civic modules.zip
#Please test this version and give me reviews and post any bugs that you found.
Click to expand...
Click to collapse
I havent tested it but any ways :good: for your work keep it coming, Nice to see dev' going on
Does this have OTG support?
Does any kernel have OTG support on XL ?
Thanks
Everything's great as same as stock..yes the touch improved and have better response but my wifi keep cut off and it stays there till manually connected..
thanks
mousemeat said:
Does this have OTG support?
Does any kernel have OTG support on XL ?
Thanks
Click to expand...
Click to collapse
No it doesnt have OTG support
faizalotai said:
Everything's great as same as stock..yes the touch improved and have better response but my wifi keep cut off and it stays there till manually connected..
thanks
Click to expand...
Click to collapse
Never happened with me though, try the newer version i updated
aniketroxx said:
Never happened with me though, try the newer version i updated
Click to expand...
Click to collapse
Ahh, now its working great..with intellidemand & intelliplug together..
Bravo...
Now have to wait for bootanimation powered by civic kernelfor my deviced..
faizalotai said:
Ahh, now its working great..with intellidemand & intelliplug together..
Bravo...
Now have to wait for bootanimation powered by civic kernelfor my deviced..
Click to expand...
Click to collapse
i already added bootanimation and now twrp version also there
aniketroxx said:
i already added bootanimation and now twrp version also there
Click to expand...
Click to collapse
That's boot image not boot animation..
i hope someone will add it here
:good:
Yeah lol lmao
Sent from my C2104 using xda app-developers app
I've waiting for twrp, and now i found on your kernel. I Like it.... thanks mate....
Sent from my C2104 using XDA Premium 4 mobile app
nice Kernel...
but hope you give a Changelog, kernel feature, and kernel source on it...
and I wanna ask btw , how to add TWRp on your kernel..?
zalzondabuzz said:
nice Kernel...
but hope you give a Changelog, kernel feature, and kernel source on it...
and I wanna ask btw , how to add TWRp on your kernel..?
Click to expand...
Click to collapse
TWRP version is there , there are two different versions . I am uploading source soon !
Glad to use your kernel buddy!! really awesome much stabler than other kernels available..THANKS @aniketroxx
#updated to new version
osm kernel
Awesome kernel!!!!! Touch feels great .....phone feeling more smooth
It'd be great for gaming!!!!!!:good:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Click to expand...
Click to collapse
Hi guys,
i've been using Nubia M2 as a testing handset and found it actually good enough as a device. So, it's pretty sad that there's almost no development for this device.
Fortunately @highwaystar_ru develop LOS 15.1 for it, and shared the kernel source here in XDA. With that available, i decide to build my personal kernel with some additions that i like.
i decide to share it here in case any other M2 users are interested.
Features & Additions
Adreno Idler
Powersuspend
Blu_active Governors
FIOPS & ZEN I/O Scheduler
Planned
Fsync Toggle - added on v2.0
Enable Westwood TCP - added on v2.1
Permissive Selinux
Download
ZIP
[url]https://drive.google.com/open?id=1f8synhtnZ98i73Ou-yyn5mKUik1M1jXx[/URL]
How to install :
Download the ZIP & Flash from TWRP
Benchmark (if that's matter for you)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks & Credit to :
@highwaystar_ru for LOS 15.1 & Kernel Source
@arter97 for Adreno Idler
@faux123 for Powersuspend
@eng.stk for Blu_active Governor
@franciscofranco for Fsync Toggle
Kernel Source
[url]https://github.com/otonieru/ASAGAO-Nubia-M2-Kernel[/URL]
Hello,
I'm using Ressurection Remix ROM for M2, based on LOS 15.1 Is it safe to flash this kernel on this ROM?
Also, it would be a good idea if you can give a little explanation of what of the implementations your doing improves the phone usage. There are a lot of newbies like me using this phone.
Anyway, thank you for your contribution.
estuardo4 said:
Hello,
I'm using Ressurection Remix ROM for M2, based on LOS 15.1 Is it safe to flash this kernel on this ROM?
Also, it would be a good idea if you can give a little explanation of what of the implementations your doing improves the phone usage. There are a lot of newbies like me using this phone.
Anyway, thank you for your contribution.
Click to expand...
Click to collapse
I never tried it with RR, since the RR Rom for this phone is not as stable as this LOS, so i choose the LOS as main base. But you can try it.
Adreno Idler and Powersuspend will help the phoneto save battery when its not used,
as for Blu_Active and Fsync, it should boost the responsiveness of the phone,
Fsync alone will increase your I/O performance quite far. Which will affect your daily UX (opening app, something like that)
otonieru said:
I never tried it with RR, since the RR Rom for this phone is not as stable as this LOS, so i choose the LOS as main base. But you can try it.
Adreno Idler and Powersuspend will help the phoneto save battery when its not used,
as for Blu_Active and Fsync, it should boost the responsiveness of the phone,
Fsync alone will increase your I/O performance quite far. Which will affect your daily UX (opening app, something like that)
Click to expand...
Click to collapse
It looks like a great addition for LOS 15, unfortunately, it didn't work on RR, it says on TWRP that ASAGAO is not for my ROM, and that the updater process ended with ERROR: 1
I'd appreciate if you can take a look at the script and the kernel from RR to see if there's a possibility to port it. I don't know how easy or hard that is.
Thank you.
estuardo4 said:
It looks like a great addition for LOS 15, unfortunately, it didn't work on RR, it says on TWRP that ASAGAO is not for my ROM, and that the updater process ended with ERROR: 1
I'd appreciate if you can take a look at the script and the kernel from RR to see if there's a possibility to port it. I don't know how easy or hard that is.
Thank you.
Click to expand...
Click to collapse
Ah, its because i create the flashing script to accomodate only model number used in LOS ROM,
Use this .IMG instead and flash from Fastboot.
https://drive.google.com/open?id=1gQBKWVfE6gfLCOeVss4xbBDDe1xYObhl
otonieru said:
Ah, its because i create the flashing script to accomodate only model number used in LOS ROM,
Use this .IMG instead and flash from Fastboot.
https://drive.google.com/open?id=1gQBKWVfE6gfLCOeVss4xbBDDe1xYObhl
Click to expand...
Click to collapse
Thank you for the IMG file. Unfortunately I won't be able to test it using Fastboot, as I don't have my computer for the next couple of days. Can I flash it using TWRP?
Edit: I tried flashing the img file within TWRP and no luck. I ended up with a bootloop. Oh well
Good afternoon! Are you planning to enable the dispersal in your core? For example, for Xiaomi MI A1, a new core with an overclocking 2.7 GHz CPU and 1000 MHz GPU.
LuigeUA said:
Good afternoon! Are you planning to enable the dispersal in your core? For example, for Xiaomi MI A1, a new core with an overclocking 2.7 GHz CPU and 1000 MHz GPU.
Click to expand...
Click to collapse
any kernel with similar implementation you can refer ?
although am not curently planning for an OC. But am open to the idea
otonieru said:
any kernel with similar implementation you can refer ?
although am not curently planning for an OC. But am open to the idea
Click to expand...
Click to collapse
make an overclocked version, please!
hi, i have LOS 15.1 in my phone but when i atempt to flash this kernel appears that ASAGAO is not for my ROM.
any idea what hapened?
oliveira. said:
hi, i have LOS 15.1 in my phone but when i atempt to flash this kernel appears that ASAGAO is not for my ROM.
any idea what hapened?
Click to expand...
Click to collapse
my script only target this model/device name :
device.name1=NX551J
device.name2=Nubia M2
device.name3=lineage_nx551j
try to check your build.prop, what is your current model/device name ? if its different from one of the three model listed above, you can change it to match one of those,
are you using highwaystar version of LOS ?
btw, you also can flash the image file i post few posts back,
use flash image feature from TWRP (use latest 3.2.1.0) or from fastboot
otonieru said:
my script only target this model/device name :
device.name1=NX551J
device.name2=Nubia M2
device.name3=lineage_nx551j
try to check your build.prop, what is your current model/device name ? if its different from one of the three model listed above, you can change it to match one of those,
are you using highwaystar version of LOS ?
btw, you also can flash the image file i post few posts back,
use flash image feature from TWRP (use latest 3.2.1.0) or from fastboot
Click to expand...
Click to collapse
nx551j
use flash image feature from TWRP (use latest 3.2.1.0) or from fastboot[/QUOTE]
System Partition?
estuardo4 said:
It looks like a great addition for LOS 15, unfortunately, it didn't work on RR, it says on TWRP that ASAGAO is not for my ROM, and that the updater process ended with ERROR: 1
I'd appreciate if you can take a look at the script and the kernel from RR to see if there's a possibility to port it. I don't know how easy or hard that is.
Thank you.
Click to expand...
Click to collapse
the problem is only in the installation script, I just added the device name used in rr and it is working. try this version.
https://drive.google.com/file/d/1zfetPrT0YoS9hlBgtcL45_K13W1jszR_/view?usp=sharing
dhannyell said:
the problem is only in the installation script, I just added the device name used in rr and it is working. try this version.
https://drive.google.com/file/d/1zfetPrT0YoS9hlBgtcL45_K13W1jszR_/view?usp=sharing
Click to expand...
Click to collapse
I check my device's names 1, 2 and 3 and all are the same as with your script, all three matches. However, when I tried to install it, the same error=1 happened. I don't know what's going on. It is really strange.
oliveira. said:
use flash image feature from TWRP (use latest 3.2.1.0) or from fastboot
Click to expand...
Click to collapse
System Partition?[/QUOTE]
NO,
Boot partition
estuardo4 said:
I check my device's names 1, 2 and 3 and all are the same as with your script, all three matches. However, when I tried to install it, the same error=1 happened. I don't know what's going on. It is really strange.
Click to expand...
Click to collapse
change the product name from rr_nx551j to lineage_nx551j
otonieru said:
change the product name from rr_nx551j to lineage_nx551j
Click to expand...
Click to collapse
Or simply add a line by calling it
Device name 4 and add lineage_nx551j
This is because 2 strings have been deleted from the original file that contains 5 and therefore the possibility to insert up to 5 device names (this is because some models like xiaomi have different names in the global or Chinese version)
Anyway thanks for this kernel will be the first of many that will be proposed I think ... for me I thank the developer as joining his kernel to my spectum settings now I can say I'm pretty satisfied
Skake said:
Or simply add a line by calling it
Device name 4 and add lineage_nx551j
This is because 2 strings have been deleted from the original file that contains 5 and therefore the possibility to insert up to 5 device names (this is because some models like xiaomi have different names in the global or Chinese version)
Anyway thanks for this kernel will be the first of many that will be proposed I think ... for me I thank the developer as joining his kernel to my spectum settings now I can say I'm pretty satisfied
Click to expand...
Click to collapse
I tried changing the device name as indicated, but still no luck.
Where do I insert the device name 4? Here's my build.prop screenshot:
I'm not a newbie, I just don't want to mess my build.prop file. Thank you.
Skake said:
Or simply add a line by calling it
Device name 4 and add lineage_nx551j
This is because 2 strings have been deleted from the original file that contains 5 and therefore the possibility to insert up to 5 device names (this is because some models like xiaomi have different names in the global or Chinese version)
Anyway thanks for this kernel will be the first of many that will be proposed I think ... for me I thank the developer as joining his kernel to my spectum settings now I can say I'm pretty satisfied
Click to expand...
Click to collapse
do you mean to add "rr_nx551j" instead as fourth line ?
because "lineage_nx551j" already there as third line
i didnt add RR yet because i didnt use RR, so i dont know how is the kernel behaviour on the ROM. Thus i suggest the user to do personal edit. Or use the .img file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* 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/Kernel
* 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.
*/
Yuki kernel is based in CAF
/* Details */
Last Xiaomi Changes
W.I.P Last CAF merges
W.I.P Upstreamed
LZ4 zram
More to come in the next few days
/* Support */
At this time, AOSP roms are not supported as the fingerprint sensor support is broken.
For now I work without the device but soon I hope to acquire it, the kernel before being released is thoroughly tested before releasing it to the public, for this, friends who own the device help me, so there will be no problems.
/* Instructions */
Simply flash the kernel zip file from the recovery.
This kernel uses Anykernel 3 so no need to reflash magisk(if you use magisk) after installing it.
Yuki Kernel Davinci
It is not necessary but if you like my job you could invite me a cup of coffee
Changelog in second post.
XDA:DevDB Information
Yuki Kernel, ROM for the Redmi K20 / Xiaomi Mi 9T
Contributors
TeamMex
Source Code: https://github.com/klozz/android_kernel_xiaomi_davinci
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Version Information
Status: Testing
Created 2020-02-25
Last Updated 2020-09-25
Reserved
Changelog:
Yuki kernel : 16/06/2020
Fod changes from Paranoid Quartz
Track Sched changes from vantom (Used in quartz kernel)
Optimized frame buffer
Import optimized memory, strchrr, string, strcpy etc
optimize memmove
Enable compat vDSO
Yuki kernel : 15/05/2020
Rebased kernel
hope reboots and audio issues are fixed now
Yuki kernel : 18/03/2020
Remove cache preloading
Remove memory optimizations
Note: seems causing problems with Xiaomi (****ty implementation) Memory optimization.
Yuki kernel : 26/02/2020
Disable Android Verified Boot (No need to flash modified vbmeta)
drm: msm: Extend qcom drm notifier
partial:drm: msm: Add fod hbm node
input: fingerprint: goodix_ta: Use qcom drm notifier
input: touchscreen: gt9886: Remove backlight notifier callback
input: touchscreen: gt9886: Use qcom drm notifier
Merge tag 'LA.UM.8.9.r1-08100-SM6xx.0' for techpack audio and data
Merge CAF tag LA.UM.8.9.r1-04400-SM6xx.0 in the kernel
Yuki kernel : 23/02/2020
Initial public build
turn on VDSO + VDSO 32bit
techpack: Include bolero
Optimized Console FrameBuffer
Align to cache and preload
optimized strrchr
arm64: Enable dcache word access
optimized memcpy and memmove
dm-crypt: increase threads
Reserved
Yuki kernel can be updated through Franco Kernel manager or similar using the following link:
http://klozz.github.io/TheXPerienceProject/downloads/device/davinci/kernel/kernel.json
Follow telegram channel for faster updates:
https://t.me/Yuki_Kernel
Bug reports:
Take a dmesg Aka kernel log
or take console-ramoops-0
using adb
Code:
adb shell cat /sys/fs/pstore/console-ramoops > ramoops.txt
reserved just in case!
thank u ...
Awesome!
Can this be flashed on miui 10 and 11?
After flashing always boots to fastboot. I had to restore my boot inage backup.
ebautista said:
After flashing always boots to fastboot. I had to restore my boot inage backup.
Click to expand...
Click to collapse
same problem here i'm on MiRoom V11
hovnonium said:
Awesome!
Can this be flashed on miui 10 and 11?
Click to expand...
Click to collapse
It does say "Android 10" required on the bottom of the first post.
So I doubt you could flash it on MIUI 10/11 running Android 9 Pie
Appreciate the work @TeamMex
If I may ask... was that Interactive I saw as a gov in there? =)
What did you use for a toolchain to compile?
ebautista said:
After flashing always boots to fastboot. I had to restore my boot inage backup.
Click to expand...
Click to collapse
Windroid-user said:
It does say "Android 10" required on the bottom of the first post.
So I doubt you could flash it on MIUI 10/11 running Android 9 Pie
Click to expand...
Click to collapse
disable VBMeta or wait next build.
Needs Miui 11 Android 10
kevp75 said:
Appreciate the work @TeamMex
If I may ask... was that Interactive I saw as a gov in there? =)
What did you use for a toolchain to compile?
Click to expand...
Click to collapse
I use clang 10
EDIT: Kernel updated read 2nd post for changes.
NetHunter
add support for NetHunter
Works on xiaomi.eu weekly ? Thanks man
I flashed it on stable 11.0.4 and it broke play store, it keeps crashing
Benfatica said:
I flashed it on stable 11.0.4 and it broke play store, it keeps crashing
Click to expand...
Click to collapse
Has nothing to do with a kernel.
Try clearing the app data, then reboot to recovery, and Wipe Cache and Dalvik.
See if it works after that
Sometimes phone randomly crashes ang goes into soft reboot, back to boot animation then goes into home screen.
liccolailo said:
Sometimes phone randomly crashes ang goes into soft reboot, back to boot animation then goes into home screen.
Click to expand...
Click to collapse
i can confirm. same issue for me as well
---------- Post added at 04:16 PM ---------- Previous post was at 04:14 PM ----------
liccolailo said:
Sometimes phone randomly crashes ang goes into soft reboot, back to boot animation then goes into home screen.
Click to expand...
Click to collapse
kevp75 said:
i can confirm. same issue for me as well
Click to expand...
Click to collapse
I need my phone f9r the weekend so I had to go backnto stock kernel. I'll flash again monday and take a log thrn.
Formating data would seem to fix softreboot issue
TeamMex said:
disable VBMeta or wait next build.
Needs Miui 11 Android 10
I use clang 10
EDIT: Kernel updated read 2nd post for changes.
Click to expand...
Click to collapse
tanks fot the kernel you cant add sound control please..
Irineu F said:
add support for NetHunter
Click to expand...
Click to collapse
i will check
doctordag91 said:
Works on xiaomi.eu weekly ? Thanks man
Click to expand...
Click to collapse
yeah my tester uses xiaomi eu
luisgonzales1977 said:
tanks fot the kernel you cant add sound control please..
Click to expand...
Click to collapse
mmm in the future yes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally Kali Nethunter is here to our beloved whyred. See Installation Instructions below. Its basically everything that you would love of you favourite ROM + nethunter! I will provide all the download links below!
Team420 Nethunter RAD x5.4 EAS Whyred
Code:
/*
* Your warranty is... still valid?
*
* 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.
*/
Code:
/*
* This is only for people who know what they are doing. This ROM is not for everyone.
* Read setup carefully. Don't flash this if you don't know what Nethunter is.
* Don't cry for help if you did not try all by yourself to fix the problems you got.
* I am not responsible for any harm done, any bricked device etc.
* This ROM is only for testing purposes and may never be applied to networks and devices you don't have the permission to pentest.
*/
The sixth release of our Nethunter kernel for Whyred (Xiaomi Redmi Note 5 Pro).
Everything is fully functional, from HID to Wifi-adapter compatibility and wlan0 in monitor mode functionality. MITMF and badUSB attacks are outdated, if they don't work, don't blame the devs.
It is based on RAD EAS Kernel, so a huge thanks to theradcolor and his hard work! (!!!)
Below are 2 different versions of our Nethunter kernels: oldcam and newcam version. So if you are having trouble with your camera on one version, just switch to the other one(your ROM camera blobs and kernel camera blobs have to match).
RAD Changelog:
• Merged Linux v4.4.238
• Merged CAF TAG LA.UM.8.2.r1-07300-sdm660.0
• ASoC: Revert queue work on system power efficient workqueue
• tcp upstreams
• net: Update WireGuard to v1.0.20200908
• configs: Disable debugfs by default
• Makefile: Parse CPU varient to KBUILD flags for GCC
• kernel/sysctl: Move sched_wakeup_granularity_ns and sched_child_runs_first to SCHED_DEBUG
• Compiled with GNU's GCC 10.2.0 with LTO
• Checkout full changelogs on Rad's GitHub.
Nethunter Changelog:
• fixed rtl8188eus driver
DOWNLOADS:
Kali NetHunter ARM64 zip
Kali NetHunter Kernel OLD CAM
Kali NetHunter Kernel NEW CAM
INSTALLATION INSTRUCTIONS:
Make sure you have an Android 10 ROM installed on your whyred, I have Lineage Os because it is a very minimal ROM.It did however also tested with CorvusOS and Nusantara Project!
Reboot into Recovery (e.g. Orange Fox)
Mount System Partition (very important else script will not continue)
Flash official nethunter arm64 generic zip
Flash the kernel zip attached in this post.
Flash latest Magisk zip.
Reboot.
Install the Nethunter App and NH Terminal via Nethunter Store (https://store.nethunter.com/) if they didn't get installed already.
Give nethunter app and terminal all permissions it asks for. Open Nethunter app and navigate to "Kali Chroot Manager" and make sure kali chroot is getting set up and started correctly.
Profit
This is NOT my work I am just sharing this
This would'nt have been possible without you Team-420!
XDA:DevDB Information
Nethunter Kernel by Team 420 , Kernel for the Xiaomi Redmi Note 5 Pro
Contributors
!codelocker!
Source Code: https://github.com/Team-420/Nethunter-Whyred-Eas
Kernel Special Features: Everything that RAD kernel provides + support for nethunter
Version Information
Status: Stable
Current Stable Version: 3.4
Created 2020-10-28
Last Updated 2020-11-28
Reserved
Reserved
reserved just in case
wow that was crazy, inbuilt wifi card went in monitor mode.
zechs said:
wow that was crazy, inbuilt wifi card went in monitor mode.
Click to expand...
Click to collapse
Haha you're welcome
There is a lot of potential with nethunter!
!codelocker! said:
Haha you're welcome
There is a lot of potential with nethunter!
Click to expand...
Click to collapse
Agreed!
Although aircrack can use monitor mode, it was unable to lock channels, it was stuck on "0" (it's scanning all channels, but can't lock on one, says "fixed channel wlan0: 0") is it because of the card or am i missing something?
Niiiceeeee :highfive:
Hats off OP - @!codelocker!
Keep the good work.
Just for info...there is another version... hope you don't mind
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-kali-nethunter-whyred-t3951286
Good luck and stay safe!
Bloody covid-19 is gonna make me an expert :laugh:
drnightshadow said:
Niiiceeeee :highfive:
Hats off OP - @!codelocker!
Keep the good work.
Just for info...there is another version... hope you don't mind
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-kali-nethunter-whyred-t3951286
Good luck and stay safe!
Bloody covid-19 is gonna make me an expert :laugh:
Click to expand...
Click to collapse
HAhahah thats a way of being productive during Covid
The link you sent is a ROM , its pretty outdated so thats why I decided to make this thread
issue with this kernel
my device went into bootloop after flashing it ,i am on lineage 17.1 rom
prathu.x said:
my device went into bootloop after flashing it ,i am on lineage 17.1 rom
Click to expand...
Click to collapse
I tested it in lineage 17.1 and it worked fine. What process did you go through ?
!codelocker! said:
I tested it in lineage 17.1 and it worked fine. What process did you go through ?
Click to expand...
Click to collapse
I flashed Pixel Experience Plus rom and now its working
Camera not workin
!codelocker! said:
I tested it in lineage 17.1 and it worked fine. What process did you go through ?
Click to expand...
Click to collapse
Camera now working used new cam kernel.zip
i m on pixel experience rom
Monitor mode not working
@!codelocker!, the link to the generic ROM in the OP is outdated (2020.3).
It has since been updated to 2020.4 (https://images.kali.org/nethunter/nethunter-2020.4-generic-arm64-kalifs-full.zip)
rahimali said:
@!codelocker!, the link to the generic ROM in the OP is outdated (2020.3).
It has since been updated to 2020.4 (https://images.kali.org/nethunter/nethunter-2020.4-generic-arm64-kalifs-full.zip)
Click to expand...
Click to collapse
Thanks , added
Not working with Pixel Experience 10 Plus.
!codelocker! said:
I tested it in lineage 17.1 and it worked fine. What process did you go through ?
Click to expand...
Click to collapse
!codelocker! said:
I tested it in lineage 17.1 and it worked fine. What process did you go through ?
Click to expand...
Click to collapse
dear admin is this work the way you mention here with lineage 17.1with nethunter2020.4 with kernel new cam have checked yet please let me know so i will do flash in my phone with orangefox recovery.
Hatty_xD said:
dear admin is this work the way you mention here with lineage 17.1with nethunter2020.4 with kernel new cam have checked yet please let me know so i will do flash in my phone with orangefox recovery.
Click to expand...
Click to collapse
worked for me , cant remember if I used new cam though,you can always change
guys the download link is not working plz provide an another one @!codelocker!
link : https://images.kali.org/nethunter/nethunter-2020.4-generic-arm64-kalifs-full.zip
where is link for kernal for note 5 pro ?
currently i am using android 8 can i try with same one or install android 10 rom and install kalinethunder
i very exited to try kali nethunter full working in note 5 pro
plz help me thank you
Suresh3112001 said:
guys the download link is not working plz provide an another one @!codelocker!
link : https://images.kali.org/nethunter/nethunter-2020.4-generic-arm64-kalifs-full.zip
where is link for kernal for note 5 pro ?
currently i am using android 8 can i try with same one or install android 10 rom and install kalinethunder
i very exited to try kali nethunter full working in note 5 pro
plz help me thank you
View attachment 5292941
Click to expand...
Click to collapse
Please, don't be troll.. use brains.. its kali official generic ROM. If you don't know that, than this is not for you "braniac".
Jesus people wanna use hack tools but not knowing the basics... ignorance is a bliss!!
And wtf is 'kernal"??? Troll, its kernel !!!
ok I will use by brain and am Sry for my bad English and know this was official ROM. but ,I found some link in the form so I Just asked for link to download rom ,I was much Beginner to hacking tools so.....
any ways Thank You
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS
Code:
/*
* We are 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 us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
This is the last release of ArrowOS, it won't receive any updates.
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
Probable lost frames when dragging the apps from app drawer to the home screen.
Be sure to include a log : check how to
DOWNLOAD (ONLY GAPPS VARIANT)
123Pan, Password: yyds
MEGA
Tip: You can flash it on TB-J607Z, but RIL won't working.
GUIDE TO FLASH
Use TWRP or OrangeFox Recovery, Download OrangeFox Recovery here: Link
Before we start, you need to make sure you have flashed recovery in both slots
Boot to recovery, switch to the other slot then reboot to recovery
Enable ADB Sideload, then sideload the package to your device
Format data if this is the first time you flash it
TIPS: DON'T FLASH MAGISK VIA ORANGEFOX RECOVERY!
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
GPL compliance:
ROM Source - https://github.com/ArrowOS
Kernel Source- https://github.com/bigsaltyfishes/kernel_lenovo_J607Z
ROM OS Version: Android 12L
ROM Kernel: Linux 4.x
ROM Firmware Required: Any firmware of Android 11, ZUI 12.5 recommended
Based On: AOSP
Device Tree: https://github.com/bigsaltyfishes/device_lenovo_J607F
Changelog:
2022-05-25
* Import Bootctrl from LA.UM.9.12.r1.14000.SMxx50.0
* Fix notification and alarm no sound issue
* Enable 2-Pane layout
* Drop IFAA
* Drop fingerprint policy
* Set default NTP Server
* Correct Boot Animation Size
As I don't have server, I need to build rom in my computer. Due to my computer resource, I can only maintain one rom. So this is the last release of ArrowOS, it won't receive any updates.
need link mega or google drive
Mr.PvT said:
need link mega or google drive
Click to expand...
Click to collapse
I've added mega link just now.
Great news, hope there will be some custom rom for the P11 Pro
I've installed your rom and it's great!
But I have discovered one bug and some missing features:
1. It's impossible to drag apps from the app drawer to the home screen
2. There is no face unlock (which exists in lenovo's stock rom)
3. The screen is not turning off when you close the case (also exists in lenovo's stock rom)
Please fix those bugs, because your rom is very good.
Does using this rom reduce widevine level?
Hello.
I'm a user of the J606F.
I looked into your git history, and it seems like a lot of work was put into it to restore the things Lenovo got rid of.
I have some question of the DT part. Lenovo deleted the DT inside our open source trees, but how did you manage to restore it? I do know that you can get the dts from the compiled dt in the boot.img but mine from the international firmware wasn't that clean.
Also, why did you do the commit https://github.com/bigsaltyfishes/k...mmit/ea7e955fe4d3869ea364b3081f717162fed32583 ?
(I'm curious what the parameter did to fix the issue)
Thanks!
bigsaltyfishes said:
As my tablet had hard brick during testing Updater in crDroid, this might be the first release also the last release.
Click to expand...
Click to collapse
What happened? Updater in crDroid, doesn't the custom fw updaters only touch the /system area?
AFAIK you don't get hard brick without touching bootloaders..
LegendOcta said:
What happened? Updater in crDroid, doesn't the custom fw updaters only touch the /system area?
AFAIK you don't get hard brick without touching bootloaders..
Click to expand...
Click to collapse
Not sure, I can't get any useful logs. My guess is that bootctl hal messes up the bootloader. I'll drop updater and won't add it to my build again, as it is hard to rescue from hard brick.
LegendOcta said:
Hello.
I'm a user of the J606F.
I looked into your git history, and it seems like a lot of work was put into it to restore the things Lenovo got rid of.
I have some question of the DT part. Lenovo deleted the DT inside our open source trees, but how did you manage to restore it? I do know that you can get the dts from the compiled dt in the boot.img but mine from the international firmware wasn't that clean.
Also, why did you do the commit https://github.com/bigsaltyfishes/k...mmit/ea7e955fe4d3869ea364b3081f717162fed32583 ?
(I'm curious what the parameter did to fix the issue)
Thanks!
Click to expand...
Click to collapse
I got dts.img from the stock boot image via unpack_bootimg and then simply decompiled it and dtbo.img. I then wrote a makefile for the decompiled source by referring to gauguin's makefile. As for why I did the commit you mentioned, it was because the compiler seems to not recognise the filenames generated by the decompiler (probably because of the commas), so I renamed them, and in fact this change fix the issue. The parameter was changed becauss I renamed source files.
bigsaltyfishes said:
I got dts.img from the stock boot image via unpack_bootimg and then simply decompiled it and dtbo.img. I then wrote a makefile for the decompiled source by referring to gauguin's makefile. As for why I did the commit you mentioned, it was because the compiler seems to not recognise the filenames generated by the decompiler (probably because of the commas), so I renamed them, and in fact this change fix the issue. The parameter was changed becauss I renamed source files.
Click to expand...
Click to collapse
Thanks a lot for the explanations.
I hope you get to recover your device.
LegendOcta said:
Thanks a lot for the explanations.
I hope you get to recover your device.
Click to expand...
Click to collapse
I also hope
Hi, will it fit for version P11 Plus 5G 256GB 8GB RAM, ZA8Y0051SE?
wins.911 said:
Hi, will it fit for version P11 Plus 5G 256GB 8GB RAM, ZA8Y0051SE?
Click to expand...
Click to collapse
No, because the P11 Plus 5G uses a different soc.
bigsaltyfishes said:
No, because the P11 Plus 5G uses a different soc.
Click to expand...
Click to collapse
HI, is it not the same soc as TB-J607Z?
My have same model, difference only 256GB and 8GB RAM.
wins.911 said:
HI, is it not the same soc as TB-J607Z?
My have same model, difference only 256GB and 8GB RAM.
Click to expand...
Click to collapse
Yes, same soc as TB-J607Z, but not same as P11 Plus (TB-J616F/TB-J616X).