I'm just wondering as I haven't seen this anywhere, xiaomi/huami didn't released kernel source for those watches, did they? Have there been any efforts to press them for it? As it has been confirmed those devices use android I'm assuming they must be useing linux kernel, is that right? If that's the case it's another GPL violation from xiaomi/huami.
I asked them if they intended to release the kernel source for the Pace. They said no.
There's currently attempts to use the kernel source for the board the watches are based on to see how far that gets but nothing of note yet
I will try to ask them the same question, I'm assuming the answer will be the same as you have received or no answer at all, but if that's the case I will contact gpl-violations for help in pressing them down about source code release. Are you able to provide a proof that those devices are running on Linux kernel? Something that is easily verifiable by looking at available binaries? I'm not really sure how to prove there is Linux inside but I guess there must be something within the binaries.
They run Android, that's proof enough
I already asked them twice, but no answer,
Asked on Facebook group, but no answer...
I think they'll never release it, but I hope I'm wrong
Surprisingly I've received the answer very quickly.
"Thank you for contacting Amazfit.
Oh somehow I was unable to include full message in the previous post. Editing it also didn't helped, anyway response from amazfit was exactly what I have expected. I'll try to press them harder.
shamus said:
Oh somehow I was unable to include full message in the previous post. Editing it also didn't helped, anyway response from amazfit was exactly what I have expected. I'll try to press them harder.
Click to expand...
Click to collapse
whats the reason for pressing them to publish the kernel source? For what do you need the source?
I understand the OSS aspect but is that all?
thaberkern said:
whats the reason for pressing them to publish the kernel source? For what do you need the source?
I understand the OSS aspect but is that all?
Click to expand...
Click to collapse
So we can build for it. Personally I'd like an Oreo build so WearOS might actually stand a chance of working
Quinny899 said:
So we can build for it. Personally I'd like an Oreo build so WearOS might actually stand a chance of working
Click to expand...
Click to collapse
just found this site
http://iwop.ingenic.com/static/iwds-releases/
from first look it seems like whe watch os is based on this verison and even look at this image, its like amazfit
{
"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"
}
I think Huami has taken over the failed OXY smartwatch: https://www.indiegogo.com/projects/oxy-smartwatch-your-daily-companion/
This seems to be the base of WatchOS. But it will be difficult to release an Oreo version of it. You will need all the drivers for the Linux kernel be Oreo compatible and then Oreo will still not run on the watch. The current Android is stripped down heavily. I think we have to wait until Ingenic releases a new version which probably only will come with a new CPU. What me worries is that the last release is from 2016. The new watches with Android 7 now have a Mediatek processor.
[EDIT]
I have just read that the processor is a MIPS processor which is not longer supported in Android. All new is using ARM. However it should not be too difficult for Huami to port their stuff over. But it will require a new watch with an ARM v7 processor. In Bip Huami is using an ARM processor as well.
SteffenBerlin said:
This seems to be the base of WatchOS. But it will be difficult to release an Oreo version of it. You will need all the drivers for the Linux kernel be Oreo compatible and then Oreo will still not run on the watch. The current Android is stripped down heavily. I think we have to wait until Ingenic releases a new version which probably only will come with a new CPU. What me worries is that the last release is from 2016. The new watches with Android 7 now have a Mediatek processor.
[EDIT]
I have just read that the processor is a MIPS processor which is not longer supported in Android. All new is using ARM. However it should not be too difficult for Huami to port their stuff over. But it will require a new watch with an ARM v7 processor. In Bip Huami is using an ARM processor as well.
Click to expand...
Click to collapse
MIPS is still supported, but will be dropped from support in the next NDK release. If Huami are sane, they'll switch to an ARM CPU, but I've been told they have some contract or connection with Ingenic to use the MIPS CPU, and there's nothing stopping them continuing to use Android 5.1 with an outdated NDK to build new watches, they just have to live with the legacy OS
This is great find hopefully this will allow to build a working kernel I'm still pushing for sources with Amazfit customer support, so far no major revelations I'm affraid.
There is interesting change of action from Huami. This is part of the email I've received today:
"Our technical team are collating the codes of our products. It would take certain time to come out with a workable way to deal with Linux Kernel. We are working our best now.
It is still of no much use. Even if you can patch a recent kernel to run on MIPS it will be far from being optimized. Same for Android. Anyway I don't understand why they are not just using their own OS on base of an ARM M4 like Garmin or Suunto but an old and deprecated Android.
SteffenBerlin said:
It is still of no much use. Even if you can patch a recent kernel to run on MIPS it will be far from being optimized. Same for Android. Anyway I don't understand why they are not just using their own OS on base of an ARM M4 like Garmin or Suunto but an old and deprecated Android.
Click to expand...
Click to collapse
In theory Android still supports MIPS, there's still generic MIPS sources being updated, just deprecated
The reason they're using an outdated Android build is that's what Ingenic provide, it's either 5.1 or 4.4/4.3
Related
The Unlegacy Android ProjectIntroduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Nexus 7 (2012) include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data only! no point of f2fs on /cache)
- SELinux in Enforcing mode
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
- We received some RIL bug reports on 3G variants - other than that, there are no known issues.
If you notice anything, be sure to report it in this thread. Stability is our main concern. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if we don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
We will have a built-in OTA updater (just like stock) soon (it's a work in progress)
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
XDA:DevDB Information
Unlegacy Android Project, ROM for the Nexus 7
Contributors
Ziyan, sheffzor
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2015-06-07
Last Updated 2017-12-23
Reserved
GApps
If you want to install GApps, we recommend Open GApps Pico.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
SafetyNet
The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!
Rooting
You can flash the latest Magisk to get rooted.
Yesss is it snappy?
I was able to workaround the panel errors in the kernel - PWM control isn't working for some reason, so I had to use an alternative method to enable backlight, meaning it's using a fixed brightness. This isn't important right now (I want the core functionality to work before making stuff bug-free). I also forward-ported the touchscreen driver, so it's mostly working now - it still needs some fixups for 3.4. My next goal: audio and video decoding.
View attachment 3350098
anzi2001 said:
Yesss is it snappy?
Click to expand...
Click to collapse
Kernel/common android-3.4 branch could be merged into the kernel after it's fixed up, which will surely make it more efficient.
great, i wish you very much success :fingers-crossed:
While I try to do my best to keep myself from working on this 24/7, I couldn't resist... and fixed camera, video encoding and decoding, and audio (party, just the rear speaker works yet) also works now :silly: what this means? Blobs won't stop us, as they work fine on 3.4 as well.
Man you really are doing the job man any way i can help? i want to help
I'm so subscribing to this
I never thought we will get to
3.4
Subbed for sure. Very good news here.
Will definitely be keeping my eye on this one.
Today, I fixed sensors and panel PWM control (meaning brightness can be changed, auto-brightness works fine as well), and Bluetooth. Doing this alone requires a huge amount of time and work, as there's still a zillion thing to do, like merging in android-3.4, fixing up touchscreen (there are ghost touches and packet spams slowing down the kernel), fixing up suspend (need to press power button multiple times to wake up), audio, otg, etc...
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
HTCDreamOn said:
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
Click to expand...
Click to collapse
do you happen to have an img for testing?
Ophidian_DarkCore said:
do you happen to have an img for testing?
Click to expand...
Click to collapse
No, you need to hardcode your pcbid and projectid into board-grouper-misc.c atm which you can get from last kmsg (just grep for those things when catting a kmsg in adb shell).
Can i help somehow? i want to help lol
I want to help too !
HTCDreamOn said:
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
Click to expand...
Click to collapse
I tried to build (img) but without success...As you said on a recent post you cannot build .img but you need to to hardcode your pcbid and projectid into board-grouper-misc.c but i dont know how to do it :S
{
"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"
}
i will subscribe to this thread, just to see how it goes...
It was a long time since i was not so excited in xda
Hi Guys, I guess you all know that Xiaomi has released an incompatible kernel source.
20.09.2016
But it is not nearly as broken as we thought it is. Thanks to Shaky (his Name in Telegram), we now know, that the bootloader has Secure Boot enabled (proof in the attachements).
This means we are not able to boot any other kernel than xiaomi's release.
We guess, there is something in the prebuilt zImage that allows the kernel to boot. Because all roms built with this zImage are booting.
21.09.2016
Its actually confirmed that the kernel that was released only works with Miui 7, so it will only boot with firmware and blobs from Miui 7.
23.09.2016
Shaky156 managed to boot a custom kernel on Miui 7.3.2 :fingers-crossed:
But WIFI is not working.
{
"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"
}
29.09.2016
Its actually confirmed that the kernel that was released only works with Miui 7, so it will only boot with firmware and blobs from Miui 7.
So today is the day :victory:
The "The Muppets" updated the blobs to work with the older bootloader. Github
Cyanogenmod updated the Device tree to build custom kernel right with the rom Github
01.10.2016
@bgcngm is working hard to update the device-tree and kernel to get CM working. There is already a booting built with kernel built from source, so stay tuned.
02.10.2016
Shaky156 said:
I have managed to boot a custom kernel on miui8 with latest firmware, unfortunately internet issues have come up so its delayed the kernel but hopefully have something published asap
Click to expand...
Click to collapse
15.10.2016
First Custom Kernel released: Brand Kernel, but still with the same bugs like every other kernel built with the rom...
And the Kernel that is provided from Xiaomi works actually, after fixing some build problems.
Now we just have to wait for the firs roms to come up with the kernel source and hopefully we can enjoy custom kernels in the near future :victory:
I will also update this Thread if there is something new.
Thanks for information !
Qualcomm Secure Boot is enabled on all phones with snapdragon. (With a few rare exceptions)
It's used for i.e verifying the trustzone image, the modem image, and the kernel when the bootloader is locked
Since your bootloader is unlocked, Secure Boot is not causing your problems
Actually bgcngm said that everything works now and it's just the matter of time when we will get a custom kernel.
Ch0rus said:
Qualcomm Secure Boot is enabled on all phones with snapdragon. (With a few rare exceptions)
It's used for i.e verifying the trustzone image, the modem image, and the kernel when the bootloader is locked
Since your bootloader is unlocked, Secure Boot is not causing your problems
Click to expand...
Click to collapse
Are you shure? Because this image was taken on a device with unlocked bootloader.
33bca said:
Are you shure? Because this image was taken on a device with unlocked bootloader.
Click to expand...
Click to collapse
Yes, Secure Boot is activated with blown fuses, and can not be disabled. It will be active even if the bootloader is unlocked, but it will not care about the kernel image when unlocked.
Ch0rus said:
Yes, Secure Boot is activated with blown fuses, and can not be disabled. It will be active even if the bootloader is unlocked, but it will not care about the kernel image when unlocked.
Click to expand...
Click to collapse
Okay that's nice, i did not know that.
Its been confirmed that the issue is only with firmware,
only a matter of time until things is happening i guess
Lets hope, pray and donating to the dev!
custom kernel can extand life of phone. I really hope xiaomi 5 will have custom kernel so i can make decision to choose mi5 than oneplus 3.
Kernels booting
[emoji39] [emoji39] [emoji39]
I can't even get the Kernel to compile
Thanks for your efforts :good:
Harrynowl said:
I can't even get the Kernel to compile
Thanks for your efforts :good:
Click to expand...
Click to collapse
The kernel, how it is now, wont compile watch on mi5devs github or mine
In mine i just fixed all the building errors, mi5devs fixed much more.
33bca said:
The kernel, how it is now, wont compile watch on mi5devs github or mine
In mine i just fixed all the building errors, mi5devs fixed much more.
Click to expand...
Click to collapse
I shall give the Mi5devs one a go. Thanks for the information
Wow nice kernel is booting , i just wanted to knw what are the issues in custom kernel beside wifi nt wrkng,?
Custom kernel CPU speed
If developers successfuly create this custom kernel that works flawlessly with Miui 8, will it be possible to change a standard Mi 5 32Gb that runs at 1.8Ghz/1.36Ghz, clocking at 2.15Ghz/1.59Ghz? This question is based on the factor that the 32Gb version is running an underclocked SD820. What do you guys think?
rcarkk said:
If developers successfuly create this custom kernel that works flawlessly with Miui 8, will it be possible to change a standard Mi 5 32Gb that runs at 1.8Ghz/1.36Ghz, clocking at 2.15Ghz/1.59Ghz? This question is based on the factor that the 32Gb version is running an underclocked SD820. What do you guys think?
Click to expand...
Click to collapse
Well if overclocking can be enabled on the msm8996 chipset with use of a custom kernel I do not see why not, assuming there are not weird perflocks although I expect the 820s found in the 32gb version may be low bin
Harrynowl said:
Well if overclocking can be enabled on the msm8996 chipset with use of a custom kernel I do not see why not, assuming there are not weird perflocks although I expect the 820s found in the 32gb version may be low bin
Click to expand...
Click to collapse
My only doubt remains on the Ram clock. The lower clocked SD820 on the Mi 5 32Gb have the Ram clocked at 1333mhz instead of the 1833mhz. I believe the 64Gb SoC is the same as the 32Gb SoC, as they sport the same 3GB of Ram.
@Shaky156 how did you get the kernel running? With what sources? Can we have a picture for proof?
BTW congrats on your 1000th post!
Hello everyone, it's a pleasure for me to share this great kernel; this is focused on stability and battery life
My dream (since I bought this phone) has been to have a kernel that suits my needs, to have great features and a rock-solid stability
I put all my time and heart to get this awesome product.
Please read this thread carefully. I will try to do my best to help you if you do the same
I'm back at it again, wishing you a happy new year and with a shiny new kernel, with a LOT newer kernel base and with a LOT of unneeded crap removed, this project has taken me more than a year to polish and I'm still doing it, but I've reached a state where I think it can be tested by you. My second m4 has completely broken (because it fell down xD), so that's why I need you guys to test it and give me feedback.
I promise you that it this is a whole different experience, you won't have any random reboots or battery drains at all
{
"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"
}
Disclaimer:
Code:
I, nor xda are responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk.
Some notes:
THIS WILL WORK ONLY ON UNLOCKED BOOTLOADERS
For now I won't be adding features because I need to finish other things
About features:
Compiled with Linaro 4.9
Improved cpu frequency scaling, before it used to ramp like crazy, and now if you aren't doing anything it will stay at the lowest freq, you can use this app to check
I've also added a wifi module replacement procedure that will Always Work(TM), regardless if it has been screwed up by other custom kernels, so you won't need to worry about no wifi and/or moving the module manually
Latest upstream Linux kernel version 3.10.108
Optimizations from LineageOS (I've based my kernel on their kernel for the msm8916 family)
This kernel is based on the latest tag of the CAF branch for the msm8916 family on nougat (LA.BR.1.2.9), which has got a lot of security and stability patches compared to our ancient stock kernel base
Cubbins' kanuti_hwid driver for bands -> The stock kernel had a really crappy solution for the mobile bands of the world regions, so this awesome guy coded a driver for this!
Pure mdss driver + pcc adjustments
Pstore support
Latest sdfat opensource filesystem, replacing the ancient and closed source tuxera module
Usb HID keyboard/mouse support you can install this and you're good to go!
Refactored bmm050 magnetometer driver
bma2x2 accelerometer sensor driver from CAF -> The stock kernel had an extremely initial and ancient version of this driver, I've spent more than a month porting it to the improved and newer driver from CAF
A LOT of cleanups everywhere, most likely you won't get to understand the big amount of removed crap so I'd suggest you to check my source repo
To control the kernel:
Use Kernel Adiutor
Installation instructions:
Just go to recovery and flash the zip!
Enjoy :')
Downloads:
https://drive.google.com/open?id=0BwBZLmXTjkbJU21neUxXZVV1UEE
Thanks To/Credits
-Cubbins, all of this hadn't been possible without his support
-The sodp guys that worked on the 3.10 AOSP kernel for tulip
-zachariasmaladroit
-AndyPhoenix9879
And other whose autorship are on my commits
Testers:
Huge thanks to them! You are enjoying this kernel because of their precious help!
@Pachops427
@Mark.05
@kamilkos16
@moustafa.badry
If you've been a tester and I haven't added you, it's because I don't know your username, so please let me know and I will add you here
XDA:DevDB Information
Destiny, Kernel for the Sony Xperia M4 Aqua
Contributors
dani020110
Source Code: https://github.com/danielgusvt/destiny
Kernel Special Features:
Version Information
Status: Testing
Created 2017-01-11
Last Updated 2017-07-22
Changelog
I will add the new changelog starting with the next build!
Reserved
Reserved
Just in case
Great! Now we can have more battery life
Hi @dani020110!
First and foremost, thanks for sharing your kernel!
After reading the mutha [email protected]#k'n thread, i did not yet find what features it does have.
You only state that we can't ask for unstable features.
Can you give us a spec list?
Thanks!
Oh and one more thing....no love for E2363?
Waancho said:
Hi @dani020110!
First and foremost, thanks for sharing your kernel!
After reading the mutha [email protected]#k'n thread, i did not yet find what features it does have.
You only state that we can't ask for unstable features.
Can you give us a spec list?
Thanks!
Oh and one more thing....no love for E2363?
Click to expand...
Click to collapse
When I have time, I add the features list and release for you variant
dani020110 said:
When I have time, I add the features list and release for you variant
Click to expand...
Click to collapse
Thanks!
Thank you so much! Finally a kernel with display control, i see in your commits you're working in Faux Sound, it isn't? I hope you can make it work, i buy the app a long time ago lol and a i want to use it lol, whatever, good work and good luck, i'm waiting the next version.
RodrigoKunJPN said:
Thank you so much! Finally a kernel with display control, i see in your commits you're working in Faux Sound, it isn't? I hope you can make it work, i buy the app a long time ago lol and a i want to use it lol, whatever, good work and good luck, i'm waiting the next version.
Click to expand...
Click to collapse
If I recalled, he had some problems with Faux Sound Control (speaker suddenly became very very quiet) so he disabled it for now.
Waancho said:
Hi @dani020110!
First and foremost, thanks for sharing your kernel!
After reading the mutha [email protected]#k'n thread, i did not yet find what features it does have.
You only state that we can't ask for unstable features.
Can you give us a spec list?
Thanks!
Oh and one more thing....no love for E2363?
Click to expand...
Click to collapse
Well, I've just added the features list; maybe today or tomorrow I'm uploading the second release and support for the E2363
hey , could you add wake gesture such as double tap to wake or it is unstable feature ?
fadyzico said:
hey , could you add wake gesture such as double tap to wake or it is unstable feature ?
Click to expand...
Click to collapse
It is a unstable feature.
What about brightness control or just lowering the brightness a little bit?
Waancho said:
Hi @dani020110!
First and foremost, thanks for sharing your kernel!
After reading the mutha [email protected]#k'n thread, i did not yet find what features it does have.
You only state that we can't ask for unstable features.
Can you give us a spec list?
Thanks!
Oh and one more thing....no love for E2363?
Click to expand...
Click to collapse
According to @EHSAN™ you can use the e2333 build
fadyzico said:
What about brightness control or just lowering the brightness a little bit?
Click to expand...
Click to collapse
Already added :,)
Does it work on E2306 with MM? Great work by the way!
ZxDax said:
Does it work on E2306 with MM? Great work by the way!
Click to expand...
Click to collapse
Yeah it does work flawlessly on E2306, I tested it because is my variant
kernel not working in sony m4 e2312
I used sony e2312 26.3B.1.33 stock android 6.0. I certainly did the right thing under the guidance and download the e2312. after flash your kernel, I restarted the sony logo But it has powered off and I've tried restarting but still did not fix the situation. I think that your kernel fails. wish you help me fix this soon
new update not working e2333
reboot at sony logo
{
"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"
}
I present to you: Kali NetHunter for the Huawei Nexus 6P Android 8.1 Oreo
This is the recommended stable version for the Nexus 6P.
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
~ Prerequisites ~
- Android 8.1 - https://developers.google.com/android/images
- TWRP - https://twrp.me/
- Magisk – https://forum.xda-developers.com/apps/magisk
~~ Downloads ~~
- NetHunter: https://www.offensive-security.com/kali-linux-nethunter-download/
~~ How to Install ~~
- Update to / flash latest official Android release
- Install TWRP
- Copy Magisk and NetHunter image to USB drive
- Reboot into TWRP, insert USB drive.
- flash NetHunter image
- flash Magisk
- Reboot
- Run NetHunter app
- Reboot
~~~ Notes & Updates ~~~
Nexmon is included in the 2020.2 release.
Credits: The Offensive Security Team and the NetHunter community, huge thanks to yesimxev, & kimocoder.
Android Version: 8.1
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the Huawei Nexus 6P
Contributors
@Re4son, @kimocoder, @yesimxev
Source Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/Re4son/android_kernel_huawei_angler
**RESERVED**
**RESERVED**
Little teaser of what more is to come
You are a man of your word.
Huge thanks to you and the entire Kali Nethunter team !
I don't how you did finally get rid of this pesky reboot bug by plugged in wlan adapter, but you delivered.
And don't disappoint.Like always.
I could go on complimenting, but as someone said to me once, back to the issue related subject on hand.
There are none.
--
Even my to an oblivion gebranded Asus NIC is working very good (with Realtek 8812au).The same goes for 8811 and the other AC ones I have.
I hadn't the time to test every single one, but I am curios if the Realtek 8811eu(s) has made it, as well.
For many people this chipset has somekind of importance, because it was the second revision of the TP-LINK TL-WN722N model.
Like you wrote, has Nexmon are couple of problems.
I could use nexutil, but solely without results.
---
I would like to thank you in the name of the Nexus community, who has held on to this device series, for one or another reason.
I will try and look, that my next device a OnePlus 7 or maybe a Xiaomi Mi 9T is going to be..
I wanted to ask if you could post a link to the most recent repository for this kernel.
I tried to build it of yours, about a week ago and couldn't pass the usb related bug.
I started to revisit the Oreo kernel for the Nvidia Shield K1 tablet, perhaps you saw the link to the posts on Twitter, over here at the shield sub-forum.
Unfortunately bricked the device a month after I finished compiling it while trying to port Linux Tegra (Ubuntu flavoured OS to the Shieldtablet..).
I kept the finished kernel.The best result did I link in the Nvidia forum at Xda and 5 other iterations are in my Afh-dev account.
I did a couple test runs yesterday, but had no luck so far.
Maybe you could take a look a the kernel and give me a hint when you have a bit free time, ..next summer?
Many heaps^
UsPdSr
edit.
The request for a link to the recent kernel source has answered itself..
Many thanks for this release. Nethunter works like a Charme
Just for those user, who like to use a other rom, than the resource hungry Google stock one, AOSiP 8.1 works just as well.
If someone rather prefers a stock environment, then SUPERXE or nrdw are a good alternative as well.
The nethunter page says the current download for 2020.2 is available. Does that mean nexmon is fully working ?
Re4son changed the Nexmon files in Nethunter's repo ~2 weeks ago again.
https://gitlab.com/kalilinux/nethun...3e47c0368acbf5878cce/oreo/angler/system/lib64
After some issues* with my 6P during testing various compatible roms for the new kernel, which reminded me painful at the last days of my previous one, which bite the dust end of last year after kimocoder's try to 'enhance' a kernel respectively released a build for android stock, which already existed to the time, based primarily on jcadduono work, revised by Re4son and then as latest working release to the official repository added.After I tried to build one by myself, supported the community(especially for this device at the time) and made pressure to the whole botched so-called "working" releases for Oreo 2 years prior.
He put some bells and whistles on it, but the massive reboots after trying to set external wlan adapter into Monitor mode, didn't let the kernel unfortunately run properly.
I am looking for a new device, but am unsure what to buy.
Beside that the Nexus nostalgic will always be a great and important factor.
Too bad that the foremost specs and the faulty hardware behave not so harmonic are over time.
I can gladly upload installer which I build a couple of days ago with the changes from Nethunter's repo.
If the Xiaomi Mi 9T wouldn't be so "full of MIUI", bootloader restrictions and Anti-Rollback protection, could it be a spectacular device.
But Xiaomi's business strategy to release every week 3 "new(sic!)" devices are a bit too generic for me, without sounding pretentious.
OnePlus is obviously the chosen candidate - Google's Pixel aren't any different from Samsung Galaxy horror show and the ridiculous expensive and at the same time sh*tty performance mastering iPhone by now. :E
The price of the OnePlus are getting affordable, some provider finally starting to pick them up here and even not everything is honkey doorey with them (firm politics have changed rapidly as well) , so are they the best-bad choice.
Sorry, I digressed.
I am happy to upload the kernel or the complete installer if prefered for you to test.
Cheers
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
@Re4son
I noticed the thread title 'rom' contained.
If possible, would I like to ask to change it into 'Overlay' or kernel.
Just for user, who are unsure about the application, function, usability of Kali Nethunter.
*
I wanted to make it clear that the device issues are to 99,9 % result of the age or his famous hardware default(s), not of this awesome work and the entire project behind.
Can't get the phone into monitor mode for the life of me.
Thanks for this very much. Im just starting to get my feet wet with this nethunter stuff. Any tips and tricks would be appreciated.
huge thanks for your work.
there is a problem: i have installed twrp,magsik,android oreo(angler-opm7.181205.001-factory-b75ce068.zip) and nethunter(nethunter-2020.2-angler-oreo-kalifs-full.zip). i could see a new HID KeyBoard Device in Win7 ,but the HID Attacks didn't work well . how can i fix this issue ?
upon flashing the file and booting , i tried opening the nethunter app , but it says "New app build detected: Doing app files update.(init.d and filesDir) and then force closes. the device is connected to the internet . what am i doing wrong ? .os is nrdw's stock optimized
crashnova said:
Can't get the phone into monitor mode for the life of me.
Thanks for this very much. Im just starting to get my feet wet with this nethunter stuff. Any tips and tricks would be appreciated.
Click to expand...
Click to collapse
The complete lack of information is overwhelming.
Which chipset?External adapter or internal chip?
;/
---------- Post added at 07:30 PM ---------- Previous post was at 07:24 PM ----------
Nightslade said:
upon flashing the file and booting , i tried opening the nethunter app , but it says "New app build detected: Doing app files update.(init.d and filesDir) and then force closes. the device is connected to the internet . what am i doing wrong ? .os is nrdw's stock optimized
Click to expand...
Click to collapse
Wipe everything and start over.
Do you build your own installer, or flashed the official release?
I had a couple of problems with Nrdw's rom, if I remember correct.It is likely to work if you fire the last stock on it, or try ABC, they are all very stable.
UsPdSr said:
The complete lack of information is overwhelming.
Which chipset?External adapter or internal chip?
;/
Click to expand...
Click to collapse
My bad. Internal, for now.
crashnova said:
My bad. Internal, for now.
Click to expand...
Click to collapse
Hm, Re4son changed the Nexmon files shortly after the pre-release and apparently fixed them.
I use it not that often and currently have I a seperate setup for work.
In any case, did I build a new installer with a freshly baked chroot, all the updates and upgrades, Apps and the currently recommended kernel for this device.
I uploaded it.
Wipe and format your device and flash afterwards the newest stock rom.
Flash Magisk and try it with the installer again.
If you encounter issues would I refer to the Kali Nethunter's gitlab presence and write a issue report.
The installer (full chroot, bootanimation, kernel..).
https://mega.nz/file/FJoAAI7A#CfAicSrguktZU8yH0X0u1BA-CH8AdWVrHlkbH13MaCk
UsPdSr said:
Wipe everything and start over.
Do you build your own installer, or flashed the official release?
I had a couple of problems with Nrdw's rom, if I remember correct.It is likely to work if you fire the last stock on it, or try ABC, they are all very stable.
Click to expand...
Click to collapse
I flashed the official release
Just after i posted this i tried with the latest stock clean install. even with no encryption and all i had the same error . Does the updating this happen for all devices ?
ill give the file you uploaded a try
Nightslade said:
I flashed the official release
Just after i posted this i tried with the latest stock clean install. even with no encryption and all i had the same error . Does the updating this happen for all devices ?
ill give the file you uploaded a try
Click to expand...
Click to collapse
Do you mean with 'update' the one recently introduced by the Nethunter team?
I assure you that is not in correlation with such bug.
Since release didn't I have a problem with one single external adapter.
As written before, do I not use nexutil often.
Re4son changed the patched firmware ~2 weeks after pre-release.
I cloned the repo, devices and build you the installer with python3.
If you have further issues would I recommend that you issue a bug report on gitlab, or write Re4son, yesimxev or kimo here..
it seems is not clear, is nexus 6p have a working monitor mode and injection working?
{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page.
Sources
Github
Same as any ROM.
Do the necessary wipes and flash the ROM.
No wipes are needed between updates from Descendant itself, unless specified.
If you're having problem with SafetyNet, please, install Magisk along the following modules:
SafetyPatcher, Magisk Hide Props or similar modules.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included along Kiwi Browser and Metro.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct
Android OS version: 11.0.0_r40
Security patch level: August
XDA:DevDB Information
Descendant XI, ROM for Treble Targets
Version Information
Status: Stable
descendant_gsi_arm64aonly-XI-Official.zip can't booting,Loop to BL.
descendant_gsi_arm64ab-XI-Official.zip Unlimited reboot.
Are Gapps included?
Edit: Yes
couldnt get it going on my device. It boots in to fastboot. Arm64a
i was very excited for this rom, but unfortunately it boots to fastboot in my moto z2 play
Gomeman said:
couldnt get it going on my device. It boots in to fastboot. Arm64a
Click to expand...
Click to collapse
Which device,can you post logs,such posts are sh......t,how can we help us when no one(since im here,9 years)post which device he use and no logs,no one can you help!Cheers!!!
Perfect on xt1962-1 moto g7 river, vzw, on top of LOS17.1
GSI targets have been updated to latest sources.
GSI devices changelog:
Solved a problem with onclite and moto g8 series that was preventing the correct display of QS.
Solved a problem that generated an erroneus display of "Debug Console" persistent notification.
Downloads at http://downloads.descendant.me/
It would be amazing to have a degoogled version of this gsi
Bootloop on Umidigi F1 Play.
LG G8X stuck on bootlanimation arm64a/b.
eltanque9 said:
It would be amazing to have a degoogled version of this gsi
Click to expand...
Click to collapse
Descendant used to be degoogled Before android 10
Samsung Galaxy M51 (SM-M515F) boot ok, not work only proximity sensor.
xabierd said:
Descendant used to be degoogled Before android 10
Click to expand...
Click to collapse
xabierd said:
Descendant used to be degoogled Before android 10
Click to expand...
Click to collapse
The main reason for which people install custom Rom/GSI is to have an OS free from bloatware/Google's rootkit....so I'll never understand the choice to build a GSI with Google's app included by default. Said this, Descendant is a very great piece of work, so thanks to developers
eltanque9 said:
...so I'll never understand the choice to build a GSI with Google's app included by default.
Click to expand...
Click to collapse
I tried a degoogled gsi once with only FOSS apps. It was hellish... None of the apps allowed me to bind my google account to restore some apps. Do i have to start my life over fresh just to get out if Google's grasp?
IamTheBRAVE said:
I tried a degoogled gsi once with only FOSS apps. It was hellish... None of the apps allowed me to bind my google account to restore some apps. Do i have to start my life over fresh just to get out if Google's grasp?
Click to expand...
Click to collapse
Degoogling is something you can't do in a single shot. For every Google's apps/services you need to find a proper alternative. Foss it's better obviously, but the point here it's not about open source vs proprietary software....it's about privacy, it's about to have respect of our freedom. We have to choice between convenience (Google, Facebook, Microsoft, etc., being a product for this advertising companies) and freedom (supporting developers and programmers who produce innovation without spying and selling users data). The hell is to be addicted to Google and Facebook craps...but I think this is clearly off topic now. PS: Mate, this is just for talk, obviously I respect your point of view
And i, yours. It's an agelong debate. No right or wrong answer... Or no answer at all☺
IamTheBRAVE said:
And i, yours. It's an agelong debate. No right or wrong answer... Or no answer at all☺
Click to expand...
Click to collapse
You're right, there is never "one truth"...and this is a really good thing
eltanque9 said:
Degoogling is something you can't do in a single shot. For every Google's apps/services you need to find a proper alternative. Foss it's better obviously, but the point here it's not about open source vs proprietary software....it's about privacy, it's about to have respect of our freedom. We have to choice between convenience (Google, Facebook, Microsoft, etc., being a product fr this advertising companies) and freedom (supporting developers and programmers who produce innovation without spying and selling users data). The hell is to be addicted to Google and Facebook craps...but I think this is clearly off topic now. PS: Mate, this is just for talk, obviously I respect your point of view
Click to expand...
Click to collapse
Thats how I run android on all my devices, some devices with microg and some others without. Gsi runa fine without google. Try to use browser or fdroid apps.
xabierd said:
Thats how I run android on all my devices, some devices with microg and some others without. Gsi runa fine without google. Try to use browser or fdroid apps.
Click to expand...
Click to collapse
This is my way too, I think I could never go back